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

Re: [RFC PATCH 0/9] Narrow/Sparse checkout round 3:

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 19, 2008, 09:06 UTC
Message-ID
<7viqtxcr1i.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<loom.20080817T094637-285@post.gmane.org>
Eric Raible <raible@gmail.com> writes:
> s/but we would need to have/but we may need/
> in the commit message?
Yeah, strictly speaking, perhaps.

One thing that I refuse to believe is we will need only one more bit and after assigning the 0x4000 bit to whatever that single purpose the index will stay that way forever. So we would need to reserve that bit as the extension bit in any case. If we do not have any extension forever, that means any index entry with the bit set is corrupt, so erroring out would be the right thing to do anyway ;-).

Previous: Eric RaibleNext: Nguyen Thai Ngoc Duy
Message 7 of 10 in “Narrow/Sparse checkout round 3: "easy mode"”
  1. 0/9 Narrow/Sparse checkout round 3: "easy mode"Nguyễn Thái Ngọc Duy, Aug 15, 2008
  2. Junio C HamanoAug 16, 2008
  3. Nguyen Thai Ngoc DuyAug 17, 2008
  4. Junio C HamanoAug 17, 2008
  5. Junio C HamanoAug 17, 2008
  6. Eric RaibleAug 17, 2008
  7. Junio C HamanoAug 19, 2008
  8. Nguyen Thai Ngoc DuyAug 17, 2008
  9. James PickensAug 19, 2008
  10. Nguyen Thai Ngoc DuyAug 30, 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.