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? - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Dec 23 08:08:10 2005
This archive was generated by hypermail 2.1.8 : 2005-12-23 08:08:18 EST