[oe] Getting patches committed

[Martin Jansa]

On Thu, Jan 21, 2010 at 01:16:26PM +0100, Rolf Leggewie wrote:
> Dr. Michael Lauer wrote:
> > I fully agree. I'm neither using patchwork nor do I find patches on the list a good idea.
> > I'd welcome for-oe-upstream trees that would contain patches that -- if good -- we could
> > just pull from.
> 
> Yes, me too would prefer to pull another branch from somewhere and
> cherry-pick from it over other solutions.
> 
> I have two questions.
> 
> 1) is it possible to host such a free-for-all branch somewhere?

Would be OK to create also branch for stuff I'm going to push upstream
soon? with developer name prefix like WIP branches ie
martin_jansa/for-oe-upstream ?

When I'm changing something far from my comfort zone, and I would like to 
discuss it on ML/get ACK before pushing. It would be nice to send just
summary to ML with link to that branch instead of whole patch-series.

And creating new branch for every occasion like this would be overkill
as branch delete needs admin hand.

> 2) although generally not a good idea, would it be possible to rebase
>    this branch frequently so that the unapplied patches always come
>    up first in "git log"?

Yes rebase would be really usefull in this type of branch also to be
able to integrate changes from ML discussion or some minor bug noticed
just after pushing. 

Also if some modified solution to some problem is already pushed to
oe.dev by someone else to see after rebase what is left and if not
needed then remove that change.

Sometimes I got feeling that I should push something ASAP as there is
high probability that someone else would like to test some new version
too and when I already have those recipes and checksums etc I want to
share at least to avoid duplicate work. 
ie xorg recipe upgrades... which I have in semi-automated way.


BTW: Maybe there should be some info from sender, if he has commit right
or not. Because if someone sends patch just for discussion (like me)
then it should be clear if someone else is needed to call 
contrib/patchwork/git-am.sh or not. (not sure how to indicate that in git
send-mail without introductory e-mail and still valid commit message)

Regards,
-- 
uin:136542059                jid:Martin.Jansa at gmail.com
Jansa Martin                 sip:jamasip at voip.wengo.fr 
JaMa