From: Nicolas Pitre <nico@cam.org>
To: Jeff King <peff@peff.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Roman Shaposhnik <rvs@sun.com>,
git@vger.kernel.org
Subject: Re: Achieving efficient storage of weirdly structured repos
Date: Sun, 06 Apr 2008 20:13:10 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.00.0804062000240.2947@xanadu.home> (raw)
In-Reply-To: <20080406161003.GA24358@coredump.intra.peff.net>
On Sun, 6 Apr 2008, Jeff King wrote:
> My thought was something like:
>
> - add a new object type, multiblob; a multiblob contains zero or more
> "child" sha1s, each of which is another multiblob or a blob. The
> data in the multiblob is an in-order concatenation of its children.
>
> - you would create multiblobs with a "smart" git-add that understands
> the filetype and splits the file accordingly (in my case, probably a
> chunk of headers and EXIF data, and then a chunk with the image
> data).
Well, in your example, the large image part should already be common to
many objects due to deltas if they're really the same: different objects
will only have different EXIF data plus a delta reference to the same
base image object. So in a way the split is already there. Needs only
that some applications exploit this information at runtime.
Nicolas
next prev parent reply other threads:[~2008-04-07 0:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 19:42 Achieving efficient storage of weirdly structured repos Roman Shaposhnik
2008-04-03 21:11 ` Linus Torvalds
2008-04-04 6:21 ` Jakub Narebski
2008-04-04 13:11 ` Nicolas Pitre
2008-04-04 14:16 ` Pieter de Bie
2008-04-05 3:24 ` Shawn O. Pearce
2008-04-04 23:30 ` Roman Shaposhnik
2008-04-04 23:57 ` Linus Torvalds
2008-04-06 0:13 ` Roman Shaposhnik
2008-04-06 0:48 ` Linus Torvalds
2008-04-06 16:10 ` Jeff King
2008-04-07 0:13 ` Nicolas Pitre [this message]
2008-04-07 0:18 ` Jeff King
2008-04-07 0:36 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.1.00.0804062000240.2947@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rvs@sun.com \
--cc=torvalds@linux-foundation.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).