Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] usermanual : update note about PR
Date: Mon, 18 Jan 2010 17:03:35 +0100	[thread overview]
Message-ID: <hj20op$t6n$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b11001171411k3183ee3fkac5144f77679658e@mail.gmail.com>

Frans Meulenbroeks wrote:
> Apart from the good practice, it also might help a little bit to give
> PR a standard location.

PR does have a standard location as defined in the StyleGuide, although
of course it may not be observed in all recipes.

http://wiki.openembedded.org/index.php/Styleguide




  parent reply	other threads:[~2010-01-18 16:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 20:32 [PATCH] barebox: Add recipe for this new bootloader Eric Benard
2010-01-17 20:51 ` Eric Bénard
2010-01-17 21:02 ` Koen Kooi
2010-01-17 21:28   ` Paul Menzel
2010-01-17 21:50     ` [PATCH] usermanual : update note about PR Eric Benard
2010-01-17 22:11       ` Frans Meulenbroeks
2010-01-18  9:24         ` Eric Bénard
2010-01-18 16:03         ` Rolf Leggewie [this message]
2010-01-18  0:31       ` Rolf Leggewie
2010-01-17 21:53     ` [PATCH] barebox: Add recipe for this new bootloader Frans Meulenbroeks
2010-01-17 23:06       ` Mike Westerhof
2010-01-18  0:22     ` Rolf Leggewie
2010-01-18 13:10       ` Phil Blundell
2010-01-18 14:28         ` Richard Purdie
2010-01-18 16:24           ` include default PR or not (was: [PATCH] barebox: Add recipe for this new bootloader) Rolf Leggewie
2010-01-21 22:53             ` Phil Blundell
2010-01-22  7:52               ` Frans Meulenbroeks
2010-01-22 16:13                 ` Khem Raj
2010-01-24 10:20                   ` include default PR or not Koen Kooi
2010-01-23 21:11               ` Rolf Leggewie
2010-01-19 20:44 ` [PATCH] barebox: Add recipe for this new bootloader Eric Bénard
2010-01-21 23:07   ` Khem Raj

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='hj20op$t6n$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --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