From: Junio C Hamano <gitster@pobox.com>
To: Eric Raible <raible@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 0/9] Narrow/Sparse checkout round 3:
Date: Tue, 19 Aug 2008 02:06:33 -0700 [thread overview]
Message-ID: <7viqtxcr1i.fsf@gitster.siamese.dyndns.org> (raw)
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 ;-).
next prev parent reply other threads:[~2008-08-19 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 14:24 [RFC PATCH 0/9] Narrow/Sparse checkout round 3: "easy mode" Nguyễn Thái Ngọc Duy
2008-08-16 10:31 ` Junio C Hamano
2008-08-17 5:12 ` Nguyen Thai Ngoc Duy
2008-08-17 5:50 ` Junio C Hamano
2008-08-17 6:10 ` Junio C Hamano
2008-08-17 9:49 ` [RFC PATCH 0/9] Narrow/Sparse checkout round 3: Eric Raible
2008-08-19 9:06 ` Junio C Hamano [this message]
2008-08-17 13:36 ` [RFC PATCH 0/9] Narrow/Sparse checkout round 3: "easy mode" Nguyen Thai Ngoc Duy
2008-08-19 21:10 ` James Pickens
2008-08-30 9:21 ` Nguyen Thai Ngoc Duy
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=7viqtxcr1i.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=raible@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).