From: Saul Wold <sgw@linux.intel.com>
To: "David Nyström" <david.c.nystrom@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Add makedevs to nativesdk, which can later allow creation of a small script which allows users of the toolchain tarball to create a custom rootfs from a package feed, using pseudo & makedevs.
Date: Fri, 20 Sep 2013 14:14:40 -0700 [thread overview]
Message-ID: <523CBAC0.1070306@linux.intel.com> (raw)
In-Reply-To: <1379598325-23165-1-git-send-email-david.nystrom@enea.com>
Please reformat the commit message to meet the guidelines
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
It should have a distinct summary: "makedevs: Add nativesdk" and then
the "why" in the body of the commit message.
Thanks
Sau!
On 09/19/2013 06:45 AM, David Nyström wrote:
> Signed-off-by: David Nyström <david.nystrom@enea.com>
> ---
> meta/recipes-devtools/makedevs/makedevs_1.0.0.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/makedevs/makedevs_1.0.0.bb b/meta/recipes-devtools/makedevs/makedevs_1.0.0.bb
> index 2b9fd37..e6860f0 100644
> --- a/meta/recipes-devtools/makedevs/makedevs_1.0.0.bb
> +++ b/meta/recipes-devtools/makedevs/makedevs_1.0.0.bb
> @@ -19,4 +19,4 @@ do_install() {
> install -m 0755 ${S}/makedevs ${D}${base_sbindir}/makedevs
> }
>
> -BBCLASSEXTEND = "native"
> +BBCLASSEXTEND = "native nativesdk"
>
prev parent reply other threads:[~2013-09-20 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 13:45 [PATCH] Add makedevs to nativesdk, which can later allow creation of a small script which allows users of the toolchain tarball to create a custom rootfs from a package feed, using pseudo & makedevs David Nyström
2013-09-20 21:14 ` Saul Wold [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=523CBAC0.1070306@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=david.c.nystrom@gmail.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 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.