From: <wenzong.fan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] oe/path.py: call /bin/cp directly
Date: Tue, 13 Aug 2013 03:09:08 -0400 [thread overview]
Message-ID: <cover.1376377523.git.wenzong.fan@windriver.com> (raw)
From: Wenzong Fan <wenzong.fan@windriver.com>
This avoids running cp with interactive mode on some hosts if defined:
alias cp='cp -i'
The following changes since commit 16d522bcd1f1b7741577fa31fab7e2129da0cae9:
maintainers.inc: reassign maintainers, remove obsolete recipes (2013-08-12 13:13:05 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib wenzong/fix_alias_cp
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/fix_alias_cp
Wenzong Fan (1):
oe/path.py: call /bin/cp directly
meta/lib/oe/path.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2013-08-13 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 7:09 wenzong.fan [this message]
2013-08-13 7:09 ` [PATCH 1/1] oe/path.py: call /bin/cp directly wenzong.fan
2013-08-16 17:11 ` Saul Wold
2013-08-19 2:07 ` wenzong fan
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=cover.1376377523.git.wenzong.fan@windriver.com \
--to=wenzong.fan@windriver.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