Hi, Dear diary, on Fri, Jul 28, 2006 at 10:51:56AM CEST, I got a letter where Johannes Schindelin <Johannes.Schindelin@xxxxxx> said that... > So the scenario is: one remote repository (probably shared), and multiple > local repositories, all tracking different branches? > > So, why not setup a single local (master) repository, setup all the other > repos with the local master as alternate, and write a simple script which > first fetches all branches into the master, and then pulls into the other > local repos from that master? Nope, the scenario is many remote repositories and any number of local repositories. Look at http://gitweb.freedesktop.org/ - as far as I know, many people have many (most?) of those repositories cloned and fetching updates is just a huge pain. This makes no assumptions about the number of local repositories, you can even fetch into various branch of a single local repository - only if you fetch into multiple repositories, all of them must see the objects you fetched. The alternative of squashing all the remote repositories into a single one is probably not very attractive since you get a huge branches tree instead, varying hooks will get impractical, it won't look good in gitweb, git clone will by default clone all the stuff, you will need to impose tag namespaces, permissions might get tricky and so on and so on. > The beauty of it is: you can still pull/push directly from the remote > repo, if you want. This should let you do that too. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Snow falling on Perl. White noise covering line noise. Hides all the bugs too. -- J. Putnam - : 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