On Tue, Oct 29, 2013 at 3:45 PM, Jakub Narębski <jna...@gmail.com> wrote:
> On 2013-10-29 14:50, Piotr Krukowiecki wrote:
> Lot of code isn't problem, see Linux kernel or GCC, or LibreOffice.org
OK, it depends on how much code is too much for you. I'm not talking
about performance of git, just disk usage. In my case I have too much
> If they are independent projects, they should get independent repositories;
> you can stitch them back together using git-submodule (or git-subtree).
> reposurgeon can hel you with that.
They are not totally independent projects (nor totally dependent).
Normally you want them all, you want to create a branch/tag on all of
them, if new directory is created you want to automatically have it
too etc. But there are use cases when you need only some of them and
then they can be seen as independent .
git-submodule have several disadvantages for my use:
- does not track branches (you have to specify hardcoded SHA1 instead
of a branch name)
- additional complexity / command layer (you have to do things like
"submodule init", "submodule update")
- you can't simply work on all submodules (you can't simply branch,
merge, commit, log, diff, etc in all submodules using one command in
git-subtree looks much better in that regard, but for example it needs
an explicit prefix (name of "subproject") on which it operates. So you
can't say "update everything" or "commit everything" etc. With
hundreds of subprojects you need another layer to automate this...
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html