RE: blobs (once more)
- From
Peter Jönsson P <peter.p.jonsson@ericsson.com>
- Date
- Apr 6, 2011, 11:12 UTC
- Message-ID
- <41F80411E3CC644A844E6BED6E472FD91196D0CD30@ESESSCMS0363.eemea.ericsson.se>
- In-Reply-To
- <vpqmxk3prki.fsf@bauges.imag.fr>
Hi!
How about using Google's repo-tool instead of submodules? Is that a better solution if one really needs to keep binaries together (in some way) with the source code?
We are starting to prototype Git and since we need to distribute cross-compilers with the code it would be nice to keep it in a separate repo. Currently we are _heavy_ ClearCase users (oh the horror) with many bad old habits that we are trying to break :)
// Peter
-----Original Message----- From: git-owner@vger.kernel.org [mailto:git-owner@vger.kernel.org] On Behalf Of Matthieu Moy Sent: den 6 april 2011 13:06 To: Pau Garcia i Quiles Cc: Git Mailing List; Johannes Schindelin Subject: Re: blobs (once more)
Pau Garcia i Quiles <pgquiles@elpauer.org> writes:
Show 13 quoted lines
> 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/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html