From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] fontconfig: specify font directory in EXTRA_OECONF
Date: Wed, 29 Jun 2011 12:36:13 +0100 [thread overview]
Message-ID: <1309347373.2551.26.camel@phil-desktop> (raw)
In-Reply-To: <4E0A7159.4020003@gmail.com>
On Tue, 2011-06-28 at 17:27 -0700, Khem Raj wrote:
> On 06/27/2011 08:24 AM, Phil Blundell wrote:
> > -PR = "r1"
> > +PR = "r3"
>
> a nitpick though not wrong but should be r2
Is it official policy that PRs need to be sequential? There seem to be
various precedents for incrementing it by more than one in a single
checkin, see for example d3fc33760a80b0a067b41ff88e99941f1c40c8f9 and
993a2367f881f1f4eaa10339cde93c7058660d67. If it's meant to only go up
by one each time then I guess I can cope with that but it would require
a bit of extra mangling at my end.
p.
next prev parent reply other threads:[~2011-06-29 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 15:24 [PATCH] fontconfig: specify font directory in EXTRA_OECONF Phil Blundell
2011-06-29 0:27 ` Khem Raj
2011-06-29 11:36 ` Phil Blundell [this message]
2011-06-29 18:29 ` Khem Raj
2011-06-29 13:35 ` Richard Purdie
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=1309347373.2551.26.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@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