From: Jakub Narebski <jnareb@gmail.com>
To: Brandon Williams <bmwill@google.com>
Cc: "Jeff Hostetler" <git@jeffhostetler.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Alex Vandiver" <alexmv@dropbox.com>,
git@vger.kernel.org, jonathantanmy@google.com, stolee@gmail.com,
sbeller@google.com, peff@peff.net, johannes.schindelin@gmx.de,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Michael Haggerty" <mhagger@alum.mit.edu>
Subject: Re: Git Merge contributor summit notes
Date: Sat, 07 Apr 2018 22:37:37 +0200 [thread overview]
Message-ID: <86tvsmeory.fsf@gmail.com> (raw)
In-Reply-To: <20180326180517.GA205538@google.com> (Brandon Williams's message of "Mon, 26 Mar 2018 11:05:17 -0700")
Brandon Williams <bmwill@google.com> writes:
> On 03/26, Jeff Hostetler wrote:
[...]
>> All of these cases could be eliminated if the type/size were available
>> in the OID.
>>
>> Just a thought. While we are converting to a new hash it seems like
>> this would be a good time to at least discuss it.
>
> Echoing what Stefan said. I don't think its a good idea to embed this
> sort of data into the OID. There are a lot of reasons but one of them
> being that would block having access to this data behind completing the
> hash transition (which could very well still be years away from
> completing).
>
> I think that a much better approach would be to create a meta-data data
> structure, much like the commit graph that stolee has been working on)
> which can store this data along side the objects (but not in the
> packfiles themselves). It could be a stacking structure which is
> periodically coalesced and we could add in a wire feature to fetch this
> meta data from the server upon fetching objects.
Well, the type of the object is available, from what I remember, in the
bitmap file for a packfile (if one does enable creaating them). There
are four compressed bit vectors, one for each type, with bit set to 1 on
i-th place if i-th object in packfile is of given type.
Just FYI.
--
Jakub Narębski
next prev parent reply other threads:[~2018-04-07 20:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 0:06 Git Merge contributor summit notes Alex Vandiver
2018-03-10 13:01 ` Ævar Arnfjörð Bjarmason
2018-03-11 0:02 ` Junio C Hamano
2018-03-12 23:40 ` Jeff King
2018-03-13 0:49 ` Brandon Williams
2018-03-12 23:33 ` Jeff King
2018-03-25 22:58 ` Ævar Arnfjörð Bjarmason
2018-03-26 17:33 ` Jeff Hostetler
2018-03-26 17:56 ` Stefan Beller
2018-03-26 18:54 ` Jeff Hostetler
2018-03-26 18:05 ` Brandon Williams
2018-04-07 20:37 ` Jakub Narebski [this message]
2018-03-26 21:00 ` Including object type and size in object id (Re: Git Merge contributor summit notes) Jonathan Nieder
2018-03-26 21:42 ` Jeff Hostetler
2018-03-26 22:40 ` Junio C Hamano
2018-03-26 20:54 ` Per-object encryption " Jonathan Nieder
2018-03-26 21:22 ` Ævar Arnfjörð Bjarmason
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=86tvsmeory.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=alexmv@dropbox.com \
--cc=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=stolee@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).