From: Junio C Hamano <junkio@cox.net>
To: David Greaves <david@dgreaves.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] core-git documentation update
Date: Sun, 08 May 2005 16:35:55 -0700 [thread overview]
Message-ID: <7v3bsx2sv8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <427E83EA.2000104@dgreaves.com> (David Greaves's message of "Sun, 08 May 2005 22:26:02 +0100")
>>>>> "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.
prev parent reply other threads:[~2005-05-08 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 17:22 [PATCH 0/2] core-git documentation update David Greaves
2005-05-08 19:38 ` Junio C Hamano
2005-05-08 21:01 ` David Greaves
2005-05-08 20:28 ` Junio C Hamano
2005-05-08 21:26 ` David Greaves
2005-05-08 23:35 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v3bsx2sv8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=david@dgreaves.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox