git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] whatchanged: customize diff-tree output

From
Alex Riesen <raa.lkml@gmail.com>
Date
Dec 22, 2005, 21:06 UTC
Message-ID
<20051222210620.GA4679@steel.home>
In-Reply-To
<Pine.LNX.4.63.0512221200190.7112@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin, Thu, Dec 22, 2005 12:16:00 +0100:
Show 12 quoted lines
> > 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?
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 5 of 9 in “Use --abbrev in git-whatchanged”
  1. Use --abbrev in git-whatchangedJohannes Schindelin, Dec 21, 2005
  2. whatchanged: customize diff-tree outputJunio C Hamano, Dec 22, 2005
  3. Linus TorvaldsDec 22, 2005
  4. Johannes SchindelinDec 22, 2005
  5. Alex RiesenDec 22, 2005
  6. Johannes SchindelinDec 22, 2005
  7. Alex RiesenDec 23, 2005
  8. Junio C HamanoDec 23, 2005
  9. Junio C HamanoDec 24, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.