From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: bunk@stusta.de, git@vger.kernel.org
Subject: Re: [PATCH] Fix empty line processing in git-shortlog.perl
Date: Mon, 7 Nov 2005 21:46:59 +0100 [thread overview]
Message-ID: <20051107204659.GT1431@pasky.or.cz> (raw)
In-Reply-To: <7v3bm9upx4.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Mon, Nov 07, 2005 at 03:56:07AM CET, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> I think the problem is deeper than that. Shortlog summarizes to
> only one line per commit, so I suspect what you would be feeding
> it would say something like this for the above example:
>
> commit f1b2646c7f2713c3ea4bce120e1d0d8091808be4
> Author: Adrian Bunk <bunk@r063144.stusta.swh.mhn.de>
>
> From: Michal Wronski <wrona@mat.uni.torun.pl>
>
> That is, the commit you quoted is done by 'git log --pretty',
> but a typical shortlog invocation would be:
>
> git log --pretty=short rev1..rev2 | git shortlog
>
> With or without your fix, the command barfs.
>
> Of course, that "From: " line should have been used as the
> commit author by the tool that created the commit out of e-mail
> Adrian received, but that is a separate issue.
Well, on a second though, I don't think we should probably handle this
at all, then. The whole logic for this in git-shortlog.perl seems to be
dubious, so would be a requirement that we require the input to be from
--pretty=short ok?
Simpler code, no bugs, everyone happy, errors during applying (like
stale From) immediately noticeable.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
prev parent reply other threads:[~2005-11-07 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 22:42 [PATCH] Fix empty line processing in git-shortlog.perl Petr Baudis
2005-11-06 22:44 ` Petr Baudis
2005-11-07 2:56 ` Junio C Hamano
2005-11-07 20:46 ` Petr Baudis [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=20051107204659.GT1431@pasky.or.cz \
--to=pasky@suse.cz \
--cc=bunk@stusta.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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