From: Alex Riesen <raa.lkml@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] whatchanged: customize diff-tree output
Date: Thu, 22 Dec 2005 22:06:20 +0100 [thread overview]
Message-ID: <20051222210620.GA4679@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.63.0512221200190.7112@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin, Thu, Dec 22, 2005 12:16:00 +0100:
> > I'm certainly ok with the short format by default. And making it
> > configurable per repo sounds fine, although at the same time I wonder if
> > that perhaps confuses people more (something that works in one project one
> > way works subtly differently in another project..)
>
> I cannot think of a saner way to have an overridable policy. Just provide
> a template config, and you're done. Everyone gets those flags per default,
> and if someone does not like it: go ahead, change it yourself!
>
> Besides, you are usually calling git-whatchanged in your private working
> tree, where not many people can change the config.
>
That's the point, isn't it? A script from ~user1/bin, which calls
git-whatchanged suddenly stops working in ~user2/repo.
Besides, how can user1 know what he has to specify to git-whatchanged
(I assume the command line overrides .git/config) so that his script
works everywhere?
Maybe such configuration better left to environment variables?
next prev parent reply other threads:[~2005-12-22 21:07 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 [this message]
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
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=20051222210620.GA4679@steel.home \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).