Re: GIT vs Other: Need argument

["Alex Riesen" <raa.lkml@gmail.com>]

On 4/25/07, Dana How <danahow@gmail.com> wrote:
> On 4/17/07, Alex Riesen <raa.lkml@gmail.com> wrote:
> > 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;

Well, as I have failed on every attempt get the idea through,
I am not sure I _have_ any useful details which can be shared.
Right at this moment I'm working on importing/exporting scripts
which hopefully can impress my colleagues enough to use git
(P4 is almost universally hated). The problem is complicated
by the fact we have to use a homegrown program which replaces
"p4 sync" (as it is somewhat handicapped in its ability to specify
what revision of what part of a project to sync).
At the moment there 4 scripts: one to workaround the mentioned
tool (unrelated to git), one to put the data into index (must use
perforce to get the real names of the files, the local names
constantly get mangled by windows), one to commit the index
along with information about the clients state (mappings aka
client specification, revision lists and custom information this
dumb tool of ours needs) and one to export git changes.
All this is very loosely connected and integrated, so I can use
them independent of each other. This also means that there
is a lot of hand work to do, though. I can share the last three
scripts, if anyone interested (the first is of no use to anyone,
except me).