From: Peter Seebach <peter.seebach@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] data_smart.py: implement _remove as a keyword like _append.
Date: Thu, 16 Aug 2012 08:32:31 -0500 [thread overview]
Message-ID: <20120816083231.4d7cb4b0@e6410-2> (raw)
In-Reply-To: <1345112026.14667.40.camel@ted>
On Thu, 16 Aug 2012 11:13:46 +0100
Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> I read this far.
>
> This is not going to make any friends. += and =+ behave differently to
> _append with immediate vs. delayed functionality. I think equating -=
> and =- is just going to confuse users even more. So no, I don't think
> we can do this.
I'm fine with dropping that part, I just put it in because it was a
pretty close analogue to +=/=+. It would not be hard to remove that.
> Why does this depend on 1/2 ?
Because I didn't think I could write it without the tracking code to
see what was happening.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2012-08-16 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 1:14 [PATCH 0/2] variable/include tracking and _remove Peter Seebach
2012-08-16 1:14 ` [PATCH 1/2] data_smart.py: track file inclusion and variable modifications Peter Seebach
2012-08-16 14:32 ` Richard Purdie
2012-08-16 16:39 ` Peter Seebach
2012-08-17 10:09 ` Richard Purdie
2012-08-16 1:14 ` [PATCH 2/2] data_smart.py: implement _remove as a keyword like _append Peter Seebach
2012-08-16 10:13 ` Richard Purdie
2012-08-16 13:32 ` Peter Seebach [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=20120816083231.4d7cb4b0@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.