Re: GIT vs Other: Need argument

From: Dana How <danahow@gmail.com>
Date: Apr 25, 2007, 08:58 UTC
Message-ID: <56b7f5510704250158v5d80feb7gb82db0da2349eb8f@mail.gmail.com>
In-Reply-To: <81b0412b0704170739te4c35f0m8e4a3cd5bad440cd@mail.gmail.com>

On 4/17/07, Alex Riesen <raa.lkml@gmail.com> wrote:

Show 12 quoted lines

> On 4/17/07, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> >  - Old school SCMs allow you to branch, but are unable to keep track
> > of merges in any meaningful way. Every time you merge, history is
> > lost. GIT (and other DSCMs) have excellent branching _and_ merging
> > facilities.
> This one was a bad argument too. Curiously, and I cannot explain why,
> ability to branch is considered a weakness of GIT ("because it confuses
> the integrators", them being old mean men). The Perforce is said to
> be "vastly superior to everything" on these grounds: "it also has
> branching support, but luckily(!) it is hard enough for simple
> developers. Was not their (Perforce's) fault, they just included it
> to keep up with the market". Almost exact wording (I had to translate it).

You are also trying to gain traction in a Perforce environment? I'd be interested in any more details you might have; I'm just starting. Email me directly if you like.

Thanks,

-- 
Dana L. How  danahow@gmail.com  +1 650 804 5991 cell