On Wednesday, April 06, 2011 at 13:12 CEST,
Peter Jönsson P <peter.p.jonsson@xxxxxxxxxxxx> wrote:
> 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?
I don't know if Repo vs. submodules is the most interesting choice;
they're both relying on plain gits for the storage. We stored large
binaries in gits for a while too, but for us the major hassle was
that it was killing our servers. When too many of the few hundreds of
developers were fetching multi-GB repos the 8-16 core 24 GB RAM server
(don't know the exact specs at the time) was really down on its knees.
Now, we were using JGit (via Gerrit) and I'm sure tuning could've helped
-- as well as just replicating the data and spreading the load across
multiple servers -- but don't forget this factor when choosing the tool.
> 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 :)
We've been there too.
--
Magnus Bäck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html