From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Pau Garcia i Quiles <pgquiles@elpauer.org>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: blobs (once more)
Date: Wed, 06 Apr 2011 13:06:21 +0200 [thread overview]
Message-ID: <vpqmxk3prki.fsf@bauges.imag.fr> (raw)
In-Reply-To: <BANLkTim3kg1ycGkgWsqaZiqMY9LTKV6DBw@mail.gmail.com> (Pau Garcia i. Quiles's message of "Wed, 6 Apr 2011 10:09:18 +0200")
Pau Garcia i Quiles <pgquiles@elpauer.org> writes:
> I have read about:
> - submodules + using different repositories once one "blob repository"
> grows too much. This will be probably rejected because it is quite
> contrived.
> - git-annex (does not get the files in when cloning, pulling, checking
> out; you need to do it manually)
> - git-media (same as git-annex)
> - boar (no, we do not want to use a VCS for binaries in addition to git)
> - and a few more
>
> So far the only good solution seems to be git-bigfiles but it's still
> in development.
This seems to be the hot topic of the moment in Git ;-). Loot at the
mailing-list's archive, like
http://thread.gmane.org/gmane.comp.version-control.git/170649
https://git.wiki.kernel.org/index.php/SoC2011Ideas#Better_big-file_support
there may be a GSoC on the topic. I don't think there's a really good
solution for you right now (but I didn't really look closely), but the
situation is improving.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2011-04-06 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 8:09 blobs (once more) Pau Garcia i Quiles
2011-04-06 9:25 ` Johannes Schindelin
2011-04-06 12:20 ` Michael J Gruber
2011-04-06 14:14 ` Martin Langhoff
2011-04-06 11:06 ` Matthieu Moy [this message]
2011-04-06 11:12 ` Peter Jönsson P
2011-04-06 16:42 ` Magnus Bäck
2011-04-07 5:20 ` Miles Bader
2011-04-07 6:45 ` 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=vpqmxk3prki.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pgquiles@elpauer.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.