From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] patman: Issue empty change logs for unchanged patches
Date: Wed, 31 Oct 2012 17:12:53 +0100 [thread overview]
Message-ID: <50914E05.5030609@denx.de> (raw)
In-Reply-To: <1351613717-7617-1-git-send-email-sjg@chromium.org>
On 10/30/2012 05:15 PM, Simon Glass wrote:
> Often a particular patch may change only for some versions of a series.
> For versions where there is no change, issue a change log indicating
> that (for example 'Changes in v4: None').
>
> For such lines, don't add a blank line afterwards, to conserve space.
> Use list.insert() instead of list = [item] + list.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Nice! That was quick! Thirsty? ;)
Tested-by: Stefan Roese <sr@denx.de>
Thanks,
Stefan
next prev parent reply other threads:[~2012-10-31 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 16:15 [U-Boot] [PATCH] patman: Issue empty change logs for unchanged patches Simon Glass
2012-10-31 16:12 ` Stefan Roese [this message]
2012-11-07 23:20 ` Anatolij Gustschin
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=50914E05.5030609@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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