Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: `PR = "r0"`: Add or not to add?
Date: Wed, 31 Aug 2011 15:49:23 +0200	[thread overview]
Message-ID: <1314798564.3769.48.camel@mattotaupa> (raw)
In-Reply-To: <j3ld1i$l0g$1@dough.gmane.org>

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

Am Mittwoch, den 31.08.2011, 15:30 +0200 schrieb Koen Kooi:
> Op 31-08-11 15:02, Otavio Salvador schreef:

[…]

> > 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.

I am sorry for the confusion. It is actually all over the place in the
user manual [1].

	$ git grep "r0" docs/

This is of course in oe.dev, but the manual is still advertised in the
Wiki [1].


Thanks,

Paul


PS: Koen, thank you for fixing your Thunderbird installation. At least
it looks good in this message.


[1] http://docs.openembedded.org/usermanual/html/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  parent reply	other threads:[~2011-08-31 13:54 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
2011-09-01 10:06                       ` Frans Meulenbroeks
2011-09-05 10:22                         ` Ahsan, Noor
2011-08-31 13:49                   ` Paul Menzel [this message]
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=1314798564.3769.48.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --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