Re: Mercurial vs Updated git HOWTO for kernel hackers

From: Sean <seanlkml@sympatico.ca>
Date: Jun 28, 2005, 23:37 UTC
Message-ID: <1765.10.10.10.24.1120001856.squirrel@linux1>
In-Reply-To: <40A9C7C2-1AFE-45BC-90A5-571628304479@mac.com>

On Tue, June 28, 2005 7:25 pm, Kyle Moffett said:

Show 8 quoted lines

> On Jun 28, 2005, at 18:59:28, Sean wrote:
>> By the sounds of it, git could just use Mecurial or some variation
>> thereof
>> as a back end.
>
> Umm, you seem to miss the point, sir.  If you use Mercurial, there is no
> reason you should layer any part of Git on top of it.  It already does
> everything that git does anyways.

No, you seem to miss the point. Git already does everything Mercurial does, and does it pretty well too. The _point_ was that if the big "feature" of Mercurial is it's on disk format, Git is perfectly capable of copying it at any point. The on disk format just ISN'T CLOSE TO BEING THE MOST IMPORTANT THING AT THE MOMENT.

Show 8 quoted lines

>
>> Git is already so much better for the things I do than BK ever was,
>> I'll
>> stick with it.
>
> This is like saying "Windows 3.1 is already so much better for the
> things
> I do than DOS ever was, I'll stick with it."  :-D

Yes, so what's your point? Mercurial is trying to solve a problem that is already perfectly well handled for me by Git. Therefore I have _zero_ motivation to direct my efforts elsewhere.

Cheers, Sean