On Tue, Nov 10, 2009 at 2:27 PM, Stefan Schmidt <ste...@datenfreihafen.org> wrote: > Hello. > > On Tue, 2009-11-10 at 14:07, Michael 'Mickey' Lauer wrote: >> >> We will do changes on the git layout, e.g. org.oe.dev is becoming >> 'master' >> and user branches will live in a seperate repository. > > While I can understand the former I can't see the reason for the later. Can > you > explain why that was decided? > > For me user and other topic branches worked well on the main repository. The > only issue I have is the flood of commits on the commit ml when a branch gets > rebased, but that is something that a filter in the commit mail hook should be > able to solve.
Splitting out user branches into separate repository gives: * option of giving developers access to push to user branches but not master branches * git clone of master repository does not pull down all users objects * namespace of master repository is not "polluted" by user branches. Working with a master and a user repository should work just as well as the current setup in all other aspects than having to do an (extra) "git remote add" command. /Esben _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
