From: Junio C Hamano <junkio@cox.net>
Date: Sun, 08 May 2005 23:35:55 GMT
Subject: Re: [PATCH 0/2] core-git documentation update
Message-ID: <7v3bsx2sv8.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <427E83EA.2000104@dgreaves.com>

>>>>> "DG" == David Greaves <david@dgreaves.com> writes:

DG> The intention now was for me to go through Linus' HEAD and verify the
DG> docs actually documented the HEAD.
DG> Then I think comparing the HEAD to jit-jc and preparing patches for that?

That one is up to you, but if your patches are against git-jc,
it would make _my_ life simpler and hopefully would make merge
easier for Linus when he returns.

After he returns, it would probably not make much sense sending
patch against git-jc, unless all of the following conditions
hold true: (1) what is already merged to git-jc conflicts with
what you are modifying, (2) all changes in git-jc are trivially
correct and veriy likely to hit Linus tree without being
rejected, and (3) Linus is too busy and lags behind git-jc.