From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qemu.inc: Use '=' for IMAGE_FSTYPES
Date: Thu, 29 Mar 2012 10:51:40 +0100 [thread overview]
Message-ID: <1333014700.14983.6.camel@ted> (raw)
In-Reply-To: <20120328232908.GA4080@bill-the-cat>
On Wed, 2012-03-28 at 16:29 -0700, Tom Rini wrote:
> On Wed, Mar 28, 2012 at 10:11:44PM +0100, Richard Purdie wrote:
> > On Wed, 2012-03-28 at 14:54 -0400, Denys Dmytriyenko wrote:
> > > On Mon, Mar 26, 2012 at 05:56:16PM +0100, Richard Purdie wrote:
> > > > On Mon, 2012-03-26 at 09:25 -0700, Tom Rini wrote:
> > > So, what is the subtle difference between += that we started with and =+ that
> > > you recommended at the end? I realize those are for append and prepend, but
> > > are they handled any different? Was your recommendation to use =+ at the end,
> > > instead of += that was used originally, based on some specifics? Thanks.
> >
> > I'm using += and =+ interchangeably. The contrast was with ?= which I
> > argued against. Order in this case doesn't matter and I have no
> > preference over += or =+, it simply doesn't matter.
>
> So I guess I'll spin everything one more time and drop the meta-intel
> version and we'll just use += since that's the common one.
Sounds good. Sorry about the churn on this one, I thought it was clear
+= and =+ were equivalent in this context.
Cheers,
Richard
prev parent reply other threads:[~2012-03-29 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 17:35 [PATCH] qemu.inc: Use '=' for IMAGE_FSTYPES Tom Rini
2012-03-26 9:15 ` Richard Purdie
2012-03-26 16:25 ` Tom Rini
2012-03-26 16:56 ` Richard Purdie
2012-03-26 17:13 ` Tom Rini
2012-03-26 18:39 ` Darren Hart
2012-03-26 19:31 ` Denys Dmytriyenko
2012-03-28 18:54 ` Denys Dmytriyenko
2012-03-28 21:11 ` Richard Purdie
2012-03-28 23:29 ` Tom Rini
2012-03-29 9:51 ` Richard Purdie [this message]
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=1333014700.14983.6.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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