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

Re: [PATCH] sha1_object_info(): be consistent with read_sha1_file()

From
Junio C Hamano <junkio@cox.net>
Date
Nov 28, 2006, 01:05 UTC
Message-ID
<7vslg4crd5.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0611280016150.30004@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> We used to try loose objects first with sha1_object_info(), but packed
> objects first with read_sha1_file(). Now, prefer packed objects over loose
> ones with sha1_object_info(), too.

Well caught. It appears this inconsistent order was from the day one when we started using the packed git, and I forgot to swap them when I did ab90ea5 to swap the reading side.

Thanks.
Previous: Johannes Schindelin
Message 2 of 2 in “sha1_object_info(): be consistent with read_sha1_file()”
  1. sha1_object_info(): be consistent with read_sha1_file()Johannes Schindelin, Nov 27, 2006
  2. Junio C HamanoNov 28, 2006

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.