From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 1/1] sysvinit-inittab: Fixed license warning.
Date: Tue, 20 Mar 2012 09:31:36 +0000 [thread overview]
Message-ID: <1332235896.9740.87.camel@ted> (raw)
In-Reply-To: <8900db51c6d31c8e968d4a582c9098e028bf85d2.1332210868.git.lianhao.lu@intel.com>
On Tue, 2012-03-20 at 10:36 +0800, Lianhao Lu wrote:
> WARNING: .../sysvinit-inittab-2.88dsf-r6/sysvinit-2.88dsf/COPYING could
> not be copied for some reason. It may not exist. WARN for now.
>
> Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
> ---
> .../recipes-core/sysvinit/sysvinit-inittab/COPYING | 339 --------------------
> .../sysvinit/sysvinit-inittab_2.88dsf.bb | 9 +-
> 2 files changed, 2 insertions(+), 346 deletions(-)
> delete mode 100644 meta/recipes-core/sysvinit/sysvinit-inittab/COPYING
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-03-20 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 2:36 [PATCH V2 0/1] warning fix of sysvinit-inittab Lianhao Lu
2012-03-20 2:36 ` [PATCH V2 1/1] sysvinit-inittab: Fixed license warning Lianhao Lu
2012-03-20 9:31 ` 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=1332235896.9740.87.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 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.