On Sunday, October 13, 2013 09:33:53 AM Brian Dolbec wrote:
> On Fri, 2013-10-11 at 14:58 -0700, Matt Turner wrote:
> > On Fri, Oct 11, 2013 at 2:11 PM, Brian Dolbec <dolsen@gentoo.org> wrote:
> > > The default tree location move is waiting on the catalyst rewrite code
> > > to go live producing stages, etc..
> > 
> > I'm exactly sure what this means, but I think you might mean something
> > like renaming master to old-master and your branch to master. That's
> > not the right way to do it, and that's not how git works.
> 
> No, completely wrong.  The default tree location is going to be moved
> from /usr/portage to somewhere in /var (they never could agree where)
> and distfiles and packages directories are being moved out of the
> PORTDIR tree directory.
> 
> Current catalyst master code has tree paths hardcoded everywhere.  Not
> only that, but the paths are often used as both a path and a variable
> name in many places.
> 
> That makes it impossible for the tree move to happen and have catalyst
> work correctly to produce stages, etc. with the new default locations.
> 
> That is why I started to work on catalyst in the first place.  But the
> code is such a mess, I couldn't stop there with the encouragement of
> many from the releng team.

I think what Matt is suggesting is that you split your rebase-on-master branch 
into logical series and send them to the list for review and merger into 
master. A Git workflow is one of incremental, reviewed changes being merged 
over time.