From: Eric Montellese <emontellese@gmail.com>
To: Scott Chacon <schacon@gmail.com>
Cc: Pete Wyckoff <pw@padd.com>, Jeff King <peff@peff.net>,
git list <git@vger.kernel.org>
Subject: Re: Fwd: Git and Large Binaries: A Proposed Solution
Date: Wed, 26 Jan 2011 11:23:45 -0500 [thread overview]
Message-ID: <AANLkTim8h7RGk59b7jsKjBEdEKaC77S7Nm2NYAE5R3i2@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimE+s81Xbj4snNX0WWxG8x=qSwaQWfK+08+1Zy+@mail.gmail.com>
Good stuff!
So, it seems like there are at least a few decent ways to work around
the git binaries problem -- but my question is, will something like
this become part of mainline git? (and how is such a decision made
and by whom?)
It does seem that there is a real need for a solution like this, and a
lot of the core code to handle it has already been written (perhaps
even by multiple folks); it's just in need (as Peff said) of a
polished and configurable script. If one were to exist, would it
become part of mainline git?
Thanks,
Eric
On Tue, Jan 25, 2011 at 10:42 PM, Scott Chacon <schacon@gmail.com> wrote:
> Hey,
>
> Sorry to come in a bit late to this, but in addition to git-annex, I
> wrote something called 'git-media' a long time ago that works in a
> similar manner to what you both are discussing.
>
> Much like what peff was talking about, it uses the smudge and clean
> filters to automatically redirect content into a .git/media directory
> instead of into Git itself while keeping the SHA in Git. One of the
> cool thing is that it can use S3, scp or a local directory to transfer
> the big files to and from.
>
> Check it out if interested:
>
> https://github.com/schacon/git-media
>
> On Sun, Jan 23, 2011 at 6:14 AM, Pete Wyckoff <pw@padd.com> wrote:
>> peff@peff.net wrote on Fri, 21 Jan 2011 17:24 -0500:
>>
>> Just a quick aside. Since (a2b665d, 2011-01-05) you can provide
>> the filename as an argument to the filter script:
>>
>> git config --global filter.huge.clean huge-clean %f
>>
>
> This is amazing. I absolutely did not know you could do this, and it
> would make parts of git-media way better if I re-implemented it using
> this. Thanks for pointing this out.
>
> Scott
>
next prev parent reply other threads:[~2011-01-26 16:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTin=UySutWLS0Y7OmuvkE=T=+YB8G8aUCxLH=GKa@mail.gmail.com>
2011-01-21 18:57 ` Fwd: Git and Large Binaries: A Proposed Solution Eric Montellese
2011-01-21 21:36 ` Wesley J. Landaker
2011-01-21 22:00 ` Eric Montellese
2011-01-21 22:24 ` Jeff King
2011-01-21 23:15 ` Eric Montellese
2011-01-22 3:05 ` Sverre Rabbelier
2011-01-23 14:14 ` Pete Wyckoff
2011-01-26 3:42 ` Scott Chacon
2011-01-26 16:23 ` Eric Montellese [this message]
2011-01-26 17:42 ` Joey Hess
2011-01-26 21:40 ` Jakub Narebski
2011-03-10 21:02 ` Alexander Miseler
2011-03-10 22:24 ` Jeff King
2011-03-13 1:53 ` Eric Montellese
2011-03-13 2:52 ` Jeff King
2011-03-13 19:33 ` Alexander Miseler
2011-03-14 19:32 ` Jeff King
2011-03-16 0:35 ` Eric Montellese
2011-03-16 14:40 ` Nguyen Thai Ngoc Duy
2011-01-22 0:07 ` Joey Hess
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=AANLkTim8h7RGk59b7jsKjBEdEKaC77S7Nm2NYAE5R3i2@mail.gmail.com \
--to=emontellese@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=pw@padd.com \
--cc=schacon@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.
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).