From: "Wesley J. Landaker" <wjl@icecavern.net>
To: Eric Montellese <emontellese@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fwd: Git and Large Binaries: A Proposed Solution
Date: Fri, 21 Jan 2011 14:36:31 -0700 [thread overview]
Message-ID: <201101211436.32033.wjl@icecavern.net> (raw)
In-Reply-To: <AANLkTimPua_kz2w33BRPeTtOEWOKDCsJzf0sqxm=db68@mail.gmail.com>
On Friday, January 21, 2011 11:57:21 Eric Montellese wrote:
> To whet your appetite to read all of the below (I know it's long),
> this is the root of the solution:
>
> --- Don't track binaries in git. Track their hashes. ---
Comment from the peanut gallery:
I haven't read your approach in great detail, but just in case you are not
aware, there is a project call git-annex <http://git-annex.branchable.com/>
by Joey Hess that I believe takes a similar approach.
Since you've obviously given this a lot of thought, you might want to take a
peek at that and see if it already does what you want, or if your proposal
does something significantly different/better.
next prev parent reply other threads:[~2011-01-21 21:36 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201101211436.32033.wjl@icecavern.net \
--to=wjl@icecavern.net \
--cc=emontellese@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.