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

Re: [PATCH 1/2] hard-code the empty tree object

From
Jeff King <peff@peff.net>
Date
Feb 15, 2008, 18:25 UTC
Message-ID
<20080215182542.GA25167@sigill.intra.peff.net>
In-Reply-To
<7vhcgaglq5.fsf@gitster.siamese.dyndns.org>
On Fri, Feb 15, 2008 at 09:42:26AM -0800, Junio C Hamano wrote:
> > Should I re-send, or do you want to just markup the existing patches?
> 
> Shouldn't the previous one that uses the hardcoded empty tree
> object name good enough that is already on 'pu'?

Yes, they are fine (I hadn't looked at them that carefully before, but it looks like you cleaned up the ordering sensibly already).

The last paragraph in the commit message of the add--interactive patch should be removed (the implementation is no longer "hack-ish").

-Peff
Previous: Junio C Hamano
Message 7 of 7 in “hard-code the empty tree object”
  1. 1/2 hard-code the empty tree objectJeff King, Feb 14, 2008
  2. Johannes SchindelinFeb 14, 2008
  3. Jeff KingFeb 14, 2008
  4. Junio C HamanoFeb 15, 2008
  5. Jeff KingFeb 15, 2008
  6. Junio C HamanoFeb 15, 2008
  7. Jeff KingFeb 15, 2008

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.