* Frederic JECKER <frederic.jecker@xxxxxxxxx> wrote: > What could I do then ? > - Use submodules ? > - Create a blessed per-project repository and instead of a public > repository for each developer create a per-project public and shared > repository ? > ...I'm a bit lost Just think about who has to see whose commits ? I guess, each project's codebase is accessed by a relatively small number of people. So it IMHO would be natural to give each project a separate (blessed) repository. The project leader will merge (or cherry-pick) the blessed changes here, and other merge-down or better rebase from there. If there's some big mainline (the base for many other projects), it should live in its own repository. BTW: you dont have to use full clones - you could also fetch individual refs if you like. Individual WIP branches probably dont necessarily need to be pushed into the central project repos - devs could sync each other selectively. cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weigelt@xxxxxxxx mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ---------------------------------------------------------------------- -- 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