Re: [PLUG] revision control systems: your faves?

[JP Vossen <jp@jpsdomain.org>]

> Date: Sat, 7 Apr 2012 10:02:50 -0400
> From: "Eric S. Raymond" <esr@thyrsus.com>
>JP Vossen <jp@jpsdomain.org>:
> > >  http://www.catb.org/~esr/writings/version-control/version-control.html
> Ah.  Somebody invoked me.:-)

Yes, that's a great article with which to bludgeon people at $WORK.


> Best reason not to go with Subversion is vulnerability to single-point
> failures. A glitch on your SVN server can completely fuck you over,
> whereas if you lose your public git server you just clone the history
> from someone's copy and keep going.

Assuming there is another copy, which for a single dev working on a 
single or small group of projects, as the OP, there might not be...  At 
least, there might not be unless on purpose for DR, which is obviously a 
Good Idea but perhaps not intuitive.

And all of the current distributed VCSs work that way, so it's a minus 
for CVS or SVN, but a wash for the new ones.


> Most of the other advice in this thread is sound.  Except: don't touch
> Perforce, it may be free-as-in-beer but is proprietary and unsafe for
> all the usual reasons proprietary is unsafe.

I strongly agree there.  Lee & I have had to agree to disagree on that 
point every time he brings that one up.  I think he will argue to "use 
the best tool for the job" which I agree with.  Where we differ is the 
criteria for and definition of "best." :-)


> And bzr - ugh. I think
> its branching model is broken, but I'm not sure because it makes my head
> hurt every time I have to re-learn it.

Can you elaborate on that?  First, I have to admit that I started with 
RCS, still use CVS *extensively* at $WORK (don't ask, but partly why I 
need a bludgeon), have used SVN for many years, and have used Bzr off 
and on for about 2 years--largely inside CVS to divorce revision control 
and publishing.  I have "investigated" git & Hg, and used git very 
slightly to get access to projects in it.

So having said all of that.  Why is bzr branching broken?  Or how does 
it differ from the others?

Later,
JP
----------------------------|:::======|-------------------------------
JP Vossen, CISSP            |:::======|      http://bashcookbook.com/
My Account, My Opinions     |=========|      http://www.jpsdomain.org/
----------------------------|=========|-------------------------------
"Microsoft Tax" = the additional hardware & yearly fees for the add-on
software required to protect Windows from its own poorly designed and
implemented self, while the overhead incidentally flattens Moore's Law.
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug