From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: `PR = "r0"`: Add or not to add?
Date: Wed, 31 Aug 2011 15:35:32 -0700 [thread overview]
Message-ID: <4E5EB734.7070802@balister.org> (raw)
In-Reply-To: <CAP9ODKpupMXbfao42zScW4aJB2X0FHwEzBBDyMH_mdCyqYAJaw@mail.gmail.com>
On 08/31/2011 06:43 AM, Otavio Salvador wrote:
> On Wed, Aug 31, 2011 at 10:30, Koen Kooi<koen@dominion.thruhere.net> wrote:
>>> Besides, this is also on the policy
>>
>> The OE classic policy maybe, not on the meta-oe policy[1].
>
> ETOOMANYPOLICIES
>
>>> so or you change the policy or you follow it. Otherwise makes no sense to
>>> have a policy if the person who merge the patches do not follow it.
>>
>> - From http://wiki.openembedded.org/index.php/Category:Policy I read:
>>
>> http://wiki.openembedded.org/index.php/Commit_Patch_Message_Guidelines
>> http://wiki.openembedded.org/index.php/Commit_Policy
>> http://wiki.openembedded.org/index.php/Commit_log_example
>> http://wiki.openembedded.org/index.php/Styleguide
>> http://wiki.openembedded.org/index.php/Versioning_Policy
>>
>> And none of those say PR = r0 is wanted behaviour. OTOH it doesn't say it's
>> unwanted either.
>
> So until it is explicit we might keep PR = r0 as it seems most people
> prefer this way.
As long as we are all chiming in, I would like to see all of us decide
once and for all what to do.
I also prefer the explicitly setting PR = "r0". Can we work out the
troublesome cases and see if we can get them fixed? Also, what is the
oe-core view on this?
Let's work out what the technical answer is and go from there.
Philip
next prev parent reply other threads:[~2011-08-31 22:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 23:06 [meta-xfce] thunar-volman: Add initial recipe with version 0.6.0 Andreas Müller
2011-08-31 7:15 ` Koen Kooi
2011-08-31 10:06 ` `PR = "r0"`: Add or not to add? (was: thunar-volman: Add initial recipe with version 0.6.0) Paul Menzel
2011-08-31 10:23 ` `PR = "r0"`: Add or not to add? Koen Kooi
2011-08-31 11:45 ` Frans Meulenbroeks
2011-08-31 11:55 ` Anders Darander
2011-08-31 12:16 ` Koen Kooi
2011-08-31 12:27 ` Paul Eggleton
2011-08-31 12:33 ` Frans Meulenbroeks
2011-08-31 12:36 ` Koen Kooi
2011-08-31 12:43 ` Anders Darander
2011-08-31 13:00 ` Koen Kooi
2011-08-31 13:19 ` Anders Darander
2011-08-31 14:10 ` Frans Meulenbroeks
2011-08-31 12:29 ` Anders Darander
2011-08-31 12:34 ` Otavio Salvador
2011-08-31 12:45 ` Koen Kooi
2011-08-31 13:02 ` Otavio Salvador
2011-08-31 13:30 ` Koen Kooi
2011-08-31 13:43 ` Otavio Salvador
2011-08-31 22:35 ` Philip Balister [this message]
2011-09-01 10:06 ` Frans Meulenbroeks
2011-09-05 10:22 ` Ahsan, Noor
2011-08-31 13:49 ` Paul Menzel
2011-08-31 14:07 ` Koen Kooi
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=4E5EB734.7070802@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.