On Tue, 10 Sep 2013, Junio C Hamano wrote:
> Nicolas Pitre <n...@fluxnic.net> writes:
> > On Tue, 10 Sep 2013, Junio C Hamano wrote:
> >> There may be trees in the wild that record 100775 or 100777 in the
> >> mode field for executable blobs, which also need to be special
> >> cased.
> > All the file mode bits are always preserved. So this is not really a
> > special case as far as the pack v4 encoding is concerned.
> Ahh. OK. It can theoretically be argued that you could further
> squeeze 13 bits out per tree entry because you would need only 5
> possible values (100644, 100755 120000, 40000, and 160000, all
> octal) for the modes, but we will never know what other modes we
> would want to use in the future, so not being over-tight and using
> 16-bit for this purpose is probably a good trade-off
Absolutely. I tried not to lose any of the currently available
extension possibilities in the canonical object format.
> (squeezing 8 bits out per tree entry would make the shape of ident
> table entry and tree path entry different and may hurt reusing the
> code to parse these tables).
One could argue that 16 bits is much more than sufficient to encode a
time zone offset too. but again this didn't seem worth painting
ourselves in a corner if ever some creative time zones are used.
Those table are also compressed. So any repetition of the same mode bit
pattern or sparseness in the tz bits is likely to be compressed well.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html