From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Shen, Cathy" <cathy.shen@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] testimage: Support full TC path such oeqa.runtime.pnp.get_memory_size in TEST_SUITES
Date: Wed, 08 Jul 2015 16:24:15 +0100 [thread overview]
Message-ID: <1436369055.9778.7.camel@linuxfoundation.org> (raw)
In-Reply-To: <9CF54C48BF4DE04F9D8FBEB712F28E401106CCF7@SHSMSX103.ccr.corp.intel.com>
On Thu, 2015-07-02 at 01:52 +0000, Shen, Cathy wrote:
> Are we OK with this patch?
To be honest, I was a bit confused as it said 1/2 and there never was a
2/2 until a week later and I didn't connect the two.
For future reference, the correct way to reference bugzilla in the
commit message is:
[YOCTO #7834]
The 2/2 patch also had no explanation of what it did in the commit
message body.
I've tweaked the commit messages for these two and queued in
master-next.
Cheers,
Richard
prev parent reply other threads:[~2015-07-08 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 7:54 [PATCH 1/2] testimage: Support full TC path such oeqa.runtime.pnp.get_memory_size in TEST_SUITES zjh
2015-07-02 1:52 ` Shen, Cathy
2015-07-08 15:24 ` 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=1436369055.9778.7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=cathy.shen@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 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.