From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Koen Kooi : angstrom 2009.X: bump automake-native to 1.10. 2 since some idiot deleted 1.10
Date: Thu, 05 Mar 2009 12:32:01 -0300 [thread overview]
Message-ID: <87bpsg2dfy.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <1236165806.10602.102.camel@andromeda> (Michael Lauer's message of "Wed, 04 Mar 2009 12:23:26 +0100")
Michael 'Mickey' Lauer <mickey@vanille-media.de> writes:
> Am Mittwoch, den 04.03.2009, 11:54 +0100 schrieb Koen Kooi:
>> On 04-03-09 11:21, Michael 'Mickey' Lauer wrote:
>> > Am Mittwoch, den 04.03.2009, 09:59 +0000 schrieb Martyn Welch:
>> >> "Review" is defined as posting it on the mailing lists and getting positive agreement from two or more core developers.
>> >
>> > Let me propose these kinds of patches being promoted in an unstable
>> > branch rather than via mailing list. This eases testing and playing
>> > around with the patch.
>>
>> Patches posted to the mailinglist get more eyes on them.
>
> More eyes but less actual testing, since it involves patching your
> current tree to be able to see the effects.
>
>> > Although there were 0 comments (among those none in favour, but also
>> > none against), I still think that org.oe.{stable,testing(dev),unstable}
>> > with a strict only-cherry-picking-from-right-to-left-allowed policy
>> > would improve our workflow and overall stability.
>>
>> That will just boil down to people only using stable or testing
>
> All but those who actually work on the branch -- which sounds like a
> good thing to me, since that's what stable and testing are about.
I belive this can be fixed using a merge window and using a pull based
model.
Instead of we do pushes against devel branch, core devels could do the
pull and we could have a -next tree the pulls automatically and reports
conflicts by mail. This is more or less what is done in Linux nowadays.
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
next prev parent reply other threads:[~2009-03-05 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090303204954.CCB9CE8008@amethyst.openembedded.net>
2009-03-03 22:25 ` [oe-commits] Koen Kooi : angstrom 2009.X: bump automake-native to 1.10. 2 since some idiot deleted 1.10 Michael 'Mickey' Lauer
2009-03-03 22:38 ` Philip Balister
2009-03-03 22:56 ` Michael 'Mickey' Lauer
2009-03-04 9:59 ` Martyn Welch
2009-03-04 10:13 ` Koen Kooi
2009-03-04 14:18 ` Martyn Welch
2009-03-04 15:43 ` Philip Balister
2009-03-04 10:21 ` Michael 'Mickey' Lauer
2009-03-04 10:54 ` Koen Kooi
2009-03-04 11:23 ` Michael 'Mickey' Lauer
2009-03-04 11:41 ` Koen Kooi
2009-03-04 15:06 ` GNUtoo
2009-03-04 11:42 ` Martyn Welch
2009-03-04 15:42 ` Philip Balister
2009-03-05 15:32 ` Otavio Salvador [this message]
2009-03-05 15:30 ` Otavio Salvador
2009-03-04 7:49 ` Frans Meulenbroeks
2009-03-04 7:55 ` Koen Kooi
2009-03-04 7:56 ` Stanislav Brabec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bpsg2dfy.fsf@neumann.lab.ossystems.com.br \
--to=otavio@ossystems.com.br \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox