From: Jakub Narebski <jnareb@gmail.com>
To: Tim Ansell <mithro@mithis.com>
Cc: git@vger.kernel.org
Subject: Re: Git and Media repositories....
Date: Fri, 07 Nov 2008 05:00:43 -0800 (PST) [thread overview]
Message-ID: <m3r65nelo1.fsf@localhost.localdomain> (raw)
In-Reply-To: <1225655428.11693.10.camel@vaio>
Tim Ansell <mithro@mithis.com> writes:
> Last week at the gittogether I lead some discussions about how we could
> make Git better support large media repositories (which is one area
> where Subversion still make sense). It was suggested that I post to this
> list to get a discussion going.
>
> The general idea is that we always clone the complete meta-data (tags,
> commits and trees) and then only clone blobs when they are needed (using
> something like alternates). This allows us to support shallow, narrow
> and sparse checkouts while still being able to perform operations such
> as committing and merging.
[...]
Well, the *workaround* you could currently use is to put large media
files in separate subdirectory, and make this subdirectory into
submodule. This uses the fact that you can selectively clone
submodules, or leave them as a stubs...
...and this is also the code you might want to look at when
implementings stubs for 'remote' blob objects
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-11-07 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 19:50 Git and Media repositories Tim Ansell
2008-11-03 6:56 ` Johannes Schindelin
2008-11-03 9:40 ` Jakub Narebski
2008-11-07 13:00 ` Jakub Narebski [this message]
2008-11-07 13:19 ` Santi Béjar
2008-11-09 4:58 ` Nguyen Thai Ngoc Duy
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=m3r65nelo1.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--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