From: Hauke Mehrtens <hauke@hauke-m.de>
To: Johannes Berg <johannes@sipsolutions.net>, backports@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH] git-tracker: remove shortlog for empty changes
Date: Mon, 02 Jun 2014 00:35:44 +0200 [thread overview]
Message-ID: <538BAAC0.5000607@hauke-m.de> (raw)
In-Reply-To: <1400658283-28439-1-git-send-email-johannes@sipsolutions.net>
On 05/21/2014 09:44 AM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> When the input tree had changes but the output doesn't get
> any changes at all, then the shortlog was being generated
> over all commits since no files were specified.
>
> Catch this special case and instead of generating a shortlog
> just add a note that no commits changed generated code.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> devel/git-tracker.py | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
Thank you for the patch, it was applied, pushed and is included in the
backports-20140501 release.
Hauke
prev parent reply other threads:[~2014-06-01 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 7:44 [PATCH] git-tracker: remove shortlog for empty changes Johannes Berg
2014-06-01 22:35 ` Hauke Mehrtens [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=538BAAC0.5000607@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
/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