From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/5] autoconf: Extend to provide nativesdk recipe
Date: Tue, 29 Nov 2011 09:12:51 +0000 [thread overview]
Message-ID: <1322557971.2140.1.camel@ted> (raw)
In-Reply-To: <4ED49F3E.2010403@windriver.com>
On Tue, 2011-11-29 at 17:00 +0800, wenzong fan wrote:
> On 11/29/2011 04:49 PM, Koen Kooi wrote:
> > Op 29 nov. 2011, om 09:39 heeft<wenzong.fan@windriver.com> <wenzong.fan@windriver.com> het volgende geschreven:
> >
> >
> >> From: Wenzong Fan<wenzong.fan@windriver.com>
> >>
> >> [YOCTO #1603]
> >>
> > For every recipe: what is '[yocto #1603]'?
>
> http://bugzilla.pokylinux.org/show_bug.cgi?id=1603
>
> The updates to each recipe was related to this requirement for yocto
> 1.2, so I add the id number in all commit messages.
What Koen is asking for in a rather cryptic fashion is for more
explanation of the change being made in the commit message. The bug ID
is fine as a reference but we shouldn't rely on that to explain what the
change is and why its needed.
Cheers,
Richard
next prev parent reply other threads:[~2011-11-29 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 8:38 [PATCH 0/5] add autotools nativesdk to meta-toolchain wenzong.fan
2011-11-29 8:38 ` [PATCH 1/5] gnu-config: Extend to provide nativesdk recipe wenzong.fan
2011-11-29 8:38 ` [PATCH 2/5] m4: Add m4-nativesdk recipes wenzong.fan
2011-11-29 17:48 ` McClintock Matthew-B29882
2011-11-29 18:04 ` Richard Purdie
2011-11-30 1:55 ` wenzong fan
2011-11-29 8:39 ` [PATCH 3/5] automake: Extend to provide nativesdk recipe wenzong.fan
2011-11-29 8:39 ` [PATCH 4/5] autoconf: " wenzong.fan
2011-11-29 8:49 ` Koen Kooi
2011-11-29 9:00 ` wenzong fan
2011-11-29 9:12 ` Richard Purdie [this message]
2011-11-29 9:14 ` Koen Kooi
2011-11-29 9:22 ` wenzong fan
2011-11-29 8:39 ` [PATCH 5/5] task-sdk-host-nativesdk: add autotools nativesdk to meta-toolchain 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=1322557971.2140.1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox