Quoting Olivier Lamy (2012-09-04 22:23:11) ... > Due to lack of support of sparse checkout in git, I (perso) don't want > we have to create a git repo per plugin etc... > IMHO That will be a pain to manage.
No longer true, git has sparse checkout support (I believe since 1.7.0). See http://git-scm.com/docs/git-read-tree.html (search for Sparse checkout section). There are multiple examples spread through the interwebs, one would be: http://jasonkarns.com/blog/subdirectory-checkouts-with-git-sparse-checkout/ And there's always shallow clones which are fine for sending format-patch(es). That said, the code should IMHO be split into repositories depending on their releases (i.e. code that gets releases simultaneously should be in one repo, code that has multiple parts which get their own release tags should be in separate repos) -- Stanislav Ochotnicky <sochotni...@redhat.com> Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
