From KRayWiki
Jump to navigation Jump to search

Preferred / Used Here



  • Pros:
  • Cons:

Concurrent Versioning System


  • CVS was the first source control system Kevin used.
  • Kevin might have used CVSNT if it was free.

Interesting / Try Later?


  • Bazaar "friendly" fork.

Web Links



  • Cons:
    • At least at some point, Mercurial was like git in that directories are not explicitly controlled.
  • Pros:
    • Apparently Mercurial has had a more stable evolution (repository structure) than Bazaar.

Tried / Not Interested



  • Don Owens probably can take the credit for Kevin trying out git.
  • Self-hosting web pages was part of the trigger to act on the intent to try it.
  • The other trigger was to find a way to use a distributed version control system. CVS has been used a lot on the home network, but the number of systems and turnover that occurs with OS re-loads, changing up which system is up today, and other what-not, has made it hard to realize a centralized CVS server. Git may work better because each system can be its own "server" with the ability to cross-connect with the other systems. We'll see.
  • Git also seemed to have more momentum that some of the other distributed systems (based on a not-at-all scientific personal review of what was out there), and the clincher was that there is a git for MSYS, which makes it more plausible for use at work.
  • Update: Abandoned working with this.
    • Tried to do something that seemed like a fairly basic version control thing: add a folder that already had files in it (without adding the files themselves).
      Git just wasn't going do that. Folders in are not explicitly controlled. They are only managed insofar as they are in a path of a controlled file.
    • While trying to learn how to use distributed features, I messed up my repository/checkout. That raised a red flag. It should not be so easy to break something like a version control system.
    • It does not help that git's keyword list is positively dizzying. Unless you work with it day in and day out, it seems unlikely one could ever get comfortable with it. Things that are relatively straight forward in other systems seem overly obscure in git. Perhaps this is not true if one is familiar with it, however, in my opinion, the mark of excellent software is inherent usability. A person well versed in use of other software should not have to inordinately struggle to grasp how to use another similar package. Even after several weeks of use, it was not "comfortable" to use.



  • The Crossfire project inspired Kevin to learn Subversion.
  • Addresses some CVS key deficiencies, but seems to create more, worse deficiencies.