[oe] OEDEM: Summary of 'OE and Poky', 'Hosting', 'Bugtracker'

[Stefan Schmidt]

Hello.

On Tue, 2009-11-10 at 15:35, Esben Haabendal wrote:
> On Tue, Nov 10, 2009 at 2:27 PM, Stefan Schmidt
> <stefan at datenfreihafen.org> wrote:
> >
> > 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

Maybe it's time to do the full step then go over to a pull based model?

> * git clone of master repository does not pull down all users objects

Is that really an issue for people?

> * namespace of master repository is not "polluted" by user branches.

The real problem is here that the git commit hooks forbid a branch delete in our
setup. If you want to ahve a branch removed you have to ping an admin.

> 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.

I know and I don't have a problem with the change. Just curious what the reasons
are. I neither have a problem with Otavios proposal that everytone should have
their own tree. The point is more about a good way of getting the changes _back
into master_. :)

regards
Stefan Schmidt