From: Junio C Hamano <gitster@pobox.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Jeff King <peff@peff.net>
Subject: Re: [RFC/PATCH] define the way new representation types are encoded in the pack
Date: Sun, 30 Oct 2011 00:11:23 -0700 [thread overview]
Message-ID: <7v4nyrrm1w.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACsJy8Cz0R_s+VYRd+1wTTfbt_vH5dd3ALgZip0xn7rfYf6gpw@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Sun, 30 Oct 2011 12:40:27 +0700")
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
> Because all blobs in this tree object must be in a fixed order, and
> they won't likely have meaningful names nor permission, should
> CAT_TREE payload is a SHA-1 sequence of all blobs (or cat-trees if we
> want nested trees) instead? IOW the tree is integrated into cat-tree
> object, not as a separate tree object.
I have no problem with that (I am not worried about minor details of the
actual implementation of cat-tree yet).
> Not sure if it's related to representation types, but is there any way
> (perhaps FLAT_BLOB type?) we can mark an object uncompressed, so we
> can mmap() and access it directly?
In pack? Loose? Both?
What kind of payload and use case do you have in mind?
next prev parent reply other threads:[~2011-10-30 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 6:04 [RFC/PATCH] define the way new representation types are encoded in the pack Junio C Hamano
2011-10-28 6:12 ` Junio C Hamano
2011-10-30 5:40 ` Nguyen Thai Ngoc Duy
2011-10-30 7:11 ` Junio C Hamano [this message]
2011-10-30 7:13 ` Junio C Hamano
2011-10-30 9:31 ` Nguyen Thai Ngoc Duy
2011-10-28 13:41 ` Jakub Narebski
2011-10-28 15:24 ` Junio C Hamano
2011-10-28 15:44 ` Shawn Pearce
2011-10-28 22:48 ` Nicolas Pitre
2011-10-28 23:07 ` Shawn Pearce
2011-10-28 23:30 ` Nicolas Pitre
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=7v4nyrrm1w.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
/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