From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: Re: [PATCH 0/1] hello-mod: Remove hello-mod example external kernel module recipe
Date: Mon, 09 Apr 2012 15:14:05 -0700 [thread overview]
Message-ID: <4F835F2D.7010304@linux.intel.com> (raw)
In-Reply-To: <cover.1333993801.git.dvhart@linux.intel.com>
On 04/09/2012 10:53 AM, Darren Hart wrote:
> The following changes since commit 1a82989345fb98becb487d270fd93a5e6dffeb47:
>
> runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:15 +0100)
>
> are available in the git repository at:
> git://git.yoctoproject.org/user-contrib/dvhart/oe-core hello-mod
> http://git.yoctoproject.org/cgit.cgi/user-contrib/dvhart/oe-core/log/?h=hello-mod
>
> Darren Hart (1):
> hello-mod: Remove hello-mod example external kernel module recipe
>
> meta/recipes-kernel/hello-mod/files/COPYING | 340 ------------------------
> meta/recipes-kernel/hello-mod/files/Makefile | 14 -
> meta/recipes-kernel/hello-mod/files/hello.c | 33 ---
> meta/recipes-kernel/hello-mod/hello-mod_0.1.bb | 15 -
> 4 files changed, 0 insertions(+), 402 deletions(-)
> delete mode 100644 meta/recipes-kernel/hello-mod/files/COPYING
> delete mode 100644 meta/recipes-kernel/hello-mod/files/Makefile
> delete mode 100644 meta/recipes-kernel/hello-mod/files/hello.c
> delete mode 100644 meta/recipes-kernel/hello-mod/hello-mod_0.1.bb
>
Can you do this as a move (git mv) instead of as a delete and re-create?
meta-skeleton is part of OE-Core if I have my git foo correct.
Thanks
Sau!
next prev parent reply other threads:[~2012-04-09 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 17:53 [PATCH 0/1] hello-mod: Remove hello-mod example external kernel module recipe Darren Hart
2012-04-09 17:53 ` [PATCH 1/1] " Darren Hart
2012-04-09 22:14 ` Saul Wold [this message]
2012-04-09 22:17 ` [PATCH 0/1] " Darren Hart
2012-04-10 15:30 ` Saul Wold
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=4F835F2D.7010304@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dvhart@linux.intel.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