Re: [PATCH/POLL] git-format-patch: the default suffix is now .patch, not .txt

From: Alex Riesen <raa.lkml@gmail.com>
Date: Jan 18, 2007, 16:05 UTC
Message-ID: <81b0412b0701180805r276fcfaq2c1582ab8e82515b@mail.gmail.com>
In-Reply-To: <20070118154257.GC15428@spearce.org>

On 1/18/07, Shawn O. Pearce <spearce@spearce.org> wrote:

Show 20 quoted lines

> > The _real_ majority of the programmers desperately need a better
> > VCS than CVS, SVN, Perforce, SourceSafe, ClearCase, etc.
>
> Yes.  But...
>
> Yesterday I had a conversation with the software configuration
> management guy at my day-time-pays-the-bills organization.
> They are seriously looking at Perforce and ClearCase, as these are
> lightyears ahead of what we have already (PVCS Version Manager).
> They also have 1-800-my-vendor telephone numbers which you can
> call and scream at someone when the tool corrupts its internal
> database[*1*], or when you cannot figure out what the "Checkout"
> action in the context menu does[*2*].
>
> However my fellow developers and I use Git.  We export our changes
> out to PVCS Version Manager via an *ugly* Perl script that I would
> never actually wish on anyone (which is one reason why its not
> contributed as git-pvcsexport).  Configuration management guy won't
> even look at Git's real strengths as it lacks the all-important
> 1-800-git-help[*3*] phone number.

Of course, he is the who'll do the yelling. It's you who'll need support. Standard Perforce replies: "it is not supported" (if you need branches as in Git), or "we will probably look into it" (if you point them to a bug. They never really do). Worst performance in the industry, too.

ClearCase had a sleep(6 /*sec*/) before writing a file in local checkouts on linux, for whatever reason :) It at least knows about oriented graphs.