From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>,
liu.ming50@gmail.com
Cc: Ming Liu <peter.x.liu@external.atlascopco.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Do not append to BBCLASSEXTEND
Date: Wed, 08 Mar 2017 23:08:15 +0000 [thread overview]
Message-ID: <1489014495.22968.81.camel@linuxfoundation.org> (raw)
In-Reply-To: <1489010552.3261.35.camel@linux.intel.com>
On Wed, 2017-03-08 at 16:02 -0600, Leonardo Sandoval wrote:
> Hi
>
> you need to send a v2 revision, following the shortlog format
>
> * Patch Do not append to BBCLASSEXTEND
> Issue Shortlog does not follow expected format
> [test_shortlog_format]
> Suggested fix Commit shortlog (first line of commit message)
> should follow the format "<target>: <summary>"
Ross actually added one when he added the patch to mut but please
remember to do this in future.
Cheers,
Richard
prev parent reply other threads:[~2017-03-08 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 14:17 [PATCH] Do not append to BBCLASSEXTEND liu.ming50
2017-03-08 22:02 ` Leonardo Sandoval
2017-03-08 23:08 ` 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=1489014495.22968.81.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=liu.ming50@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.x.liu@external.atlascopco.com \
/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.