From: Junio C Hamano <junkio@cox.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Linus Torvalds <torvalds@osdl.org>,
git@vger.kernel.org
Subject: Re: [PATCH] whatchanged: customize diff-tree output
Date: Sat, 24 Dec 2005 01:44:27 -0800 [thread overview]
Message-ID: <7vzmmqu8w4.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20051223182047.GB3165@steel.home
> But you cannot know which ones you have to give, unless you parsed
> output of git-repo-config!
Why?
I was suggesting that you would literally write something like
this in your script:
git-whatchanged --name-status "$1".."$2"
Then whatchanged uses the '--name-status', and ignores whatever
is in the repository configuration, so you do not need to care
what repo-config says. Neither used are its built-in defaults.
prev parent reply other threads:[~2005-12-24 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 22:37 [PATCH] Use --abbrev in git-whatchanged Johannes Schindelin
2005-12-22 6:21 ` [PATCH] whatchanged: customize diff-tree output Junio C Hamano
2005-12-22 6:48 ` Linus Torvalds
2005-12-22 11:16 ` Johannes Schindelin
2005-12-22 21:06 ` Alex Riesen
2005-12-22 22:24 ` Johannes Schindelin
2005-12-23 18:12 ` Alex Riesen
2005-12-23 4:19 ` Junio C Hamano
[not found] ` <20051223182047.GB3165@steel.home>
2005-12-24 9: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=7vzmmqu8w4.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=torvalds@osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).