From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: include default PR or not
Date: Sun, 24 Jan 2010 11:20:26 +0100 [thread overview]
Message-ID: <hjh6t9$6v0$1@ger.gmane.org> (raw)
In-Reply-To: <19c1b8a91001220813w46f8888ewcffb90df590bda93@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22-01-10 17:13, Khem Raj wrote:
> IMO Letting PR=r0 is better because it does help people in remembering
> to bump PR when they make the first change after r0
> afterall 0 is also a number so it does convey some information in the recipe.
My experience is that people forget to bump PR regardless of PR = rX
being present in the recipe and/or includes, that line of thinking is moot.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLXB7qMkyGM64RGpERAh9dAKCOEMCbtp+JMVdjqmpIJeAwO0sxuQCfXUbN
6ggZc7oVtJXYhraPeNIwSIw=
=/Bkw
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-24 10:23 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
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 ` Koen Kooi [this message]
2010-01-23 21:11 ` include default PR or not 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='hjh6t9$6v0$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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