Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
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: Wed, 04 Mar 2009 10:42:39 -0500	[thread overview]
Message-ID: <49AEA16F.3020402@balister.org> (raw)
In-Reply-To: <49AE6924.2090903@gefanuc.com>

[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]

Martyn Welch wrote:
> Michael 'Mickey' Lauer wrote:
>> 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.
>>
> 
> But had a patch deleting multiple versions of a core package been posted 
> to the mailing list, people would have had a chance to object. In some 
> cases the effect that a patch will have can be quite evident enough by 
> looking at it, the patch wouldn't necessarily have needed to actually 
> have been applied.

I think both approaches have merit. Patches sent to the list get more 
exposure, but there are some changes that will benefit from preparing 
the change in a branch so it is easier for people to do some tests.

Mickey's suggestion may even work well with patches reviewed on the 
list. I need to read his email when I am not trying to get on a plane :)

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2009-03-04 15:47 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 [this message]
2009-03-05 15:32               ` Otavio Salvador
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=49AEA16F.3020402@balister.org \
    --to=philip@balister.org \
    --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