From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Support for passing path to custom map in git-shortlog.perl
Date: Mon, 07 Nov 2005 14:44:25 -0800 [thread overview]
Message-ID: <7vr79sqdrq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051107215412.GU1431@pasky.or.cz> (Petr Baudis's message of "Mon, 7 Nov 2005 22:54:12 +0100")
Petr Baudis <pasky@suse.cz> writes:
> ... I think it can be useful - either when you
> want to work on readonly tree, or when you want to support custom
> mailmap in addition to the default project's one without interference...
Ah, that sort of makes sense. On the other hand you could run
git-shortlog in a separate directory right now by piping the
git-log output to "(cd somewhere && git-shortlog)", so...
Come to think of it, why not make git-shortlog take the same set
of parameters as git-log takes (perhaps except --pretty)? Then
the issues you raised starts to make sense and we would
certainly want -m MAPFILE option there.
prev parent reply other threads:[~2005-11-07 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 23:07 [PATCH] Support for passing path to custom map in git-shortlog.perl Petr Baudis
2005-11-07 0:11 ` Junio C Hamano
2005-11-07 21:54 ` Petr Baudis
2005-11-07 22:44 ` Junio C Hamano [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=7vr79sqdrq.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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.