From: Jeff King <peff@peff.net>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: John Szakmeister <john@szakmeister.net>, git@vger.kernel.org
Subject: Re: Zero padded file modes...
Date: Thu, 5 Sep 2013 15:10:38 -0400 [thread overview]
Message-ID: <20130905191038.GA15910@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.2.03.1309051302570.14472@syhkavp.arg>
On Thu, Sep 05, 2013 at 01:09:34PM -0400, Nicolas Pitre wrote:
> On Thu, 5 Sep 2013, Jeff King wrote:
>
> > There are basically two solutions:
> >
> > 1. Add a single-bit flag for "I am 0-padded in the real data". We
> > could probably even squeeze it into the same integer.
> >
> > 2. Have a "classic" section of the pack that stores the raw object
> > bytes. For objects which do not match our expectations, store them
> > raw instead of in v4 format. They will not get the benefit of v4
> > optimizations, but if they are the minority of objects, that will
> > only end up with a slight slow-down.
>
> That is basically what I just suggested. But instead of a special
> section, simply using a special object type number would do it.
Yeah, I think we are in agreement. I only suggested a separate section
because I hadn't carefully read the v4 patches yet, and didn't know if
there was room in the normal sequence. A special object number seems
much more elegant.
-Peff
next prev parent reply other threads:[~2013-09-05 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 14:00 Zero padded file modes John Szakmeister
2013-09-05 15:36 ` Jeff King
2013-09-05 16:18 ` Duy Nguyen
2013-09-05 16:33 ` Jeff King
2013-09-05 16:56 ` Nicolas Pitre
2013-09-05 16:25 ` A Large Angry SCM
2013-09-05 17:09 ` Nicolas Pitre
2013-09-05 19:10 ` Jeff King [this message]
2013-09-05 17:13 ` John Szakmeister
2013-09-05 19:35 ` Jeff King
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=20130905191038.GA15910@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=john@szakmeister.net \
--cc=nico@fluxnic.net \
/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).