Re: Updated handling of the git repositories

Hi Kohei,

On 2010-08-25 at 09:23 -0400, Kohei Yoshida wrote:

> > All this is very new, so use on your own risk ;-)  Specifically, at
> > the moment, the master repositories are not really open for big
> > commits, we have to see first how it works, polish it a bit, etc.
> > Ideally, only build-related stuff should go there for now.  Risky and
> > experimental stuff, as well as cws backports should stay as patches.
> 
> What I'm very anxious to know is when we will open these master repos
> for large patches.  One advantage of using git to manage patches is to
> (finally) avoid having to adjust large feature patches.  So, to me the
> ability to be able to commit large changes to the master repos is
> absolutely crucial.

Oh - hard to say an exact date.  I'd say the best would be after the 3.3
release - I think we'll have enough experience with smaller patches at
that time [ie. if the new approach really works, etc. :-)]

> Having said this, I'm all for being safe than sorry and conducting
> migration slowly with caution.  So, please don't take this as my attempt
> to push things (it is not).

But what you can do ~immediately is to setup your private repo(s) on
fd.o, clone them to <ooo-build>/clone/, and work there.  To get them to
the 'official' ooo-build, you'd create & commit snapshots of that as
patches in the apply file.

Regards,
Kendy