Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-29 Thread Junqian Gordon Xu
On 03/28/2008 10:49 AM, Koen Kooi wrote: > | FWIW, in my experience getting a fix from .dev into stable is about a > 1 day > | turnaround. What might help to speed this up would be some sort of cool > | shell script in contrib to help generate the mtn log listing to post for > | review (koen ?) Unf

Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-28 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bernhard Guillon schreef: | Koen Kooi wrote: |> It doesn't matter how you turn matters, a commit to the stable branch |> requires review on this mailinglist. Machine mentors are developers by |> definition, so you only need one more developer to sign o

Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-28 Thread Bernhard Guillon
Koen Kooi wrote: > It doesn't matter how you turn matters, a commit to the stable branch > requires review on this mailinglist. Machine mentors are developers by > definition, so you only need one more developer to sign off on your > backport. > Please someone sign off or at least say the backpo

Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-28 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bernhard Guillon schreef: | Koen Kooi wrote: |> If you want to get stuff in quicker, you should apply for commit access |> to oe.dev. |> |> | This will not help a machine mentor to get backports which are already | included into .dev branch into Angstr

Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-28 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hans Henry von Tresckow schreef: | On Fri, Mar 28, 2008 at 6:29 AM, Bernhard Guillon < | [EMAIL PROTECTED]> wrote: | |> Koen Kooi wrote: |>> If you want to get stuff in quicker, you should apply for commit access |>> to oe.dev. |>> |>> |> This will not

Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-28 Thread Hans Henry von Tresckow
On Fri, Mar 28, 2008 at 6:29 AM, Bernhard Guillon < [EMAIL PROTECTED]> wrote: > Koen Kooi wrote: > > If you want to get stuff in quicker, you should apply for commit access > > to oe.dev. > > > > > This will not help a machine mentor to get backports which are already > included into .dev branch i

Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-28 Thread Bernhard Guillon
Koen Kooi wrote: > If you want to get stuff in quicker, you should apply for commit access > to oe.dev. > > This will not help a machine mentor to get backports which are already included into .dev branch into Angstrom stable branch. It will only help to get changes into .dev branch. best rega

Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-28 Thread Florian Boor
Hi, Koen Kooi schrieb: > If you want to get stuff in quicker, you should apply for commit access > to oe.dev. this does not answer his request. Just for the records: I would like to see this changed as well since the machine mentors are responsible for (un-)breaking support for their devices anyw

Re: [Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-28 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bernhard Guillon schreef: | Hello Angstrom community, | should we change the backport policy to be more open? | We have machine mentors for different devices. Some devices are only | used by few developers. And the more Angstrom is supporting different

[Angstrom-devel] [RFC] Machine mentors and machine backport patch reviews policy change

2008-03-27 Thread Bernhard Guillon
Hello Angstrom community, should we change the backport policy to be more open? We have machine mentors for different devices. Some devices are only used by few developers. And the more Angstrom is supporting different machines the more difficult it will be to review stuff which only affects one