Re: Source Code Control



andrew queisser wrote:
I remember VSS from before it was a MS product and it was bad back then so I
don't blame MS for anything.

You might as well blame them for being dumb enough to buy it. By putting
the Microsoft name on it, they have foisted it off on far more
unsuspecting customers that the original company could have.

I once worked for a company that migrated (despite my protests) from CVS
to VSS. Apparently the engineers doing GUI development (for an embedded
system) didn't like using the command-line interface to CVS. I pointed
out that there were at least four GUI interfaces available for CVS at
that time, but apparently they thought wanted an "official" GUI, rather
than something a third party "hacked together". They also used the
standard FUD about wanting a company to sue if there was a problem,
though I've never heard of anyone succeeding at suing MS over a
software failure.

Apparently they hadn't noticed (and didn't believe when told) that third
party "hacked together" software is often much better than the stuff
from MS.
.



Relevant Pages

  • Re: Configuration Management
    ... Is there a GUI ... It appears that CVS is quite popular (per a simple search ... -- http://www.blastwave.org/ for solaris pre-packaged binaries with pkg-get Organized by the author of pkg-get ...
    (comp.unix.solaris)
  • Re: exec problems
    ... > I am not running any GUI using TK, just a simple script run from ... > tclsh. ... > fail because there is no valid CVS session active. ... If you're using CVS in a terminal in a GUI, ...
    (comp.lang.tcl)
  • Re: Great SWT Program
    ... on GUI basics and it will be as natural to use as breathing -- I know. ... CVS, making Eclipse interoperate with it is going to be tough, ...
    (comp.lang.java.programmer)
  • Re: Version Control
    ... >In a previus incarnation I used SCCS and tools like that. ... CVS + CVL.app gui is what I use. ...
    (uk.comp.sys.mac)
  • Re: Windopes. Its all about LIES AND DENIAL.
    ... > Blame the hardware. ... > Blame the configuration. ... > Blame the gui. ... This is written into the bible of typical windope help desk guidelines ...
    (comp.os.linux.misc)