From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "McClintock Matthew-B29882" <B29882@freescale.com>,
"Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 1/2] Add new strace-graph package to avoid making perl a dependecy for all of strace
Date: Mon, 31 Oct 2011 09:05:46 +0000 [thread overview]
Message-ID: <201110310905.49436.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <CAEsOVNd+p0U59Gpf+mA_cywMhOcnspbhe9xB2JvS2fhF31T1_g@mail.gmail.com>
On Friday 28 October 2011 21:07:44 McClintock Matthew-B29882 wrote:
> On Fri, Oct 28, 2011 at 10:54 AM, Phil Blundell <philb@gnu.org> wrote:
> > That logic sounds reasonable, but I think Richard's point was that it's
> > more conventional to use "=+" rather than an override for prepending.
>
> I sort of forgot that += and =+ are different. Shall I resubmit this patch?
Yes please.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-10-31 9:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 5:14 [PATCH 1/2] Add new strace-graph package to avoid making perl a dependecy for all of strace Matthew McClintock
2011-10-27 5:14 ` [PATCH 2/2] Add new util-linux-chkdupexe package to avoid making perl a dependecy for all of util-linux Matthew McClintock
2011-10-27 7:32 ` Richard Purdie
2011-10-27 7:26 ` [PATCH 1/2] Add new strace-graph package to avoid making perl a dependecy for all of strace Richard Purdie
2011-10-27 19:31 ` [PATCH v2 " Matthew McClintock
2011-10-28 8:55 ` Richard Purdie
2011-10-28 15:34 ` McClintock Matthew-B29882
2011-10-28 15:54 ` Phil Blundell
2011-10-28 20:07 ` McClintock Matthew-B29882
2011-10-31 9:05 ` Paul Eggleton [this message]
2011-10-31 16:26 ` [PATCH v3 " Matthew McClintock
2011-11-02 0:35 ` Saul Wold
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=201110310905.49436.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=B29882@freescale.com \
--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