From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] image.bbclass, kernel.bbclass: remove non-standard -n option from cp command
Date: Tue, 23 Aug 2011 18:28:53 -0700 [thread overview]
Message-ID: <1314149333.5939.66.camel@rex> (raw)
In-Reply-To: <d61dc1988ac39cc249f94588d5453e9b90298f75.1314112712.git.paul.eggleton@linux.intel.com>
On Tue, 2011-08-23 at 16:22 +0100, Paul Eggleton wrote:
> -n is not a POSIX option and does not work on some systems (e.g. Debian
> Lenny); in any case it is not strictly necessary here, so remove it.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> meta/classes/image.bbclass | 2 +-
> meta/classes/kernel.bbclass | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-08-24 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 15:22 [PATCH 0/1] Remove cp -n option as discussed v2 Paul Eggleton
2011-08-23 15:22 ` [PATCH 1/1] image.bbclass, kernel.bbclass: remove non-standard -n option from cp command Paul Eggleton
2011-08-23 18:26 ` Darren Hart
2011-08-24 1:28 ` 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=1314149333.5939.66.camel@rex \
--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