From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org, Tim Ansell <mithro@mithis.com>
Subject: Re: [RFC/PATCH 2/3] replace_object: add mechanism to replace objects found in "refs/replace/"
Date: Sat, 10 Jan 2009 08:30:39 -0800 (PST) [thread overview]
Message-ID: <m3tz87yvh4.fsf@localhost.localdomain> (raw)
In-Reply-To: <7v8wpl4akr.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Christian Couder <chriscool@tuxfamily.org> writes:
>
> > Yeah, but read_sha1_file is called to read all object files, not just
> > commits. So putting the hook there will:
> >
> > 1) add a lookup overhead when reading any object,
> > 2) make it possible to replace any object,
>
> I actually see (2) as an improvement, and (1) as an associated cost.
I just had an idea: we can use this mechanism to better manage large
binary files in Git, by using replacements for _blobs_.
We want to be able to have two flavours of repository: one with large
blobs (media files usually), and one without. We can use stubs in the
place of large binary files in 'no-megablobs' flavor, and add contents
of those files via refs/replace/* for _blobs_ in 'with-megablobs'
flavour. We can control which objects we want to have, and which
objects to transfer.
What do you think about this (abuse of) an idea?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-01-10 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 7:43 [RFC/PATCH 2/3] replace_object: add mechanism to replace objects found in "refs/replace/" Christian Couder
2009-01-07 8:41 ` Junio C Hamano
2009-01-08 17:31 ` Christian Couder
2009-01-08 23:55 ` Junio C Hamano
2009-01-10 16:30 ` Jakub Narebski [this message]
[not found] ` <1231727868.6716.155.camel@vaio>
2009-01-12 9:50 ` Jakub Narebski
2009-01-07 12:29 ` Johannes Schindelin
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=m3tz87yvh4.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mithro@mithis.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).