git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] core-git documentation update

From
Junio C Hamano <junkio@cox.net>
Date
May 8, 2005, 23:35 UTC
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.

Previous: David Greaves
Message 6 of 6 in “core-git documentation update”
  1. 0/2 core-git documentation updateDavid Greaves, May 8, 2005
  2. Junio C HamanoMay 8, 2005
  3. David GreavesMay 8, 2005
  4. Junio C HamanoMay 8, 2005
  5. David GreavesMay 8, 2005
  6. Junio C HamanoMay 8, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.