fredag 23 februari 2007 02:07 skrev Johannes Schindelin: > Hi, > > On Fri, 23 Feb 2007, Han-Wen Nienhuys wrote: > > > nitpick: > > > > \n > > > > for newline would be nice. Similar for backslash, formfeed, alarm, etc. > > Yes, I thought about that. But it would change behaviour (even if I don't > think it would do serious damage; the only user of interpolate.[ch] I saw > is git-daemon, and that does not need \n, I guess). Other tools that come to mind, rpm and clearcase use \n vfor newline in the format argument, which is good because I can guess that even without looking at the documentation. %n I'd guess would be for a number of some kind, e..g. the ordinal number of the commit listed (in subset and order of the listed commits) > Besides, "%n" is > > - more consistent, with...? > - date(1) does it the same way, and Ok, I learnt something. Never fi > - you can put BS, FF, AL, etc. into the format string before passing > it as an option to git; git does not have to help you there. They are hard to type in shells and even harder in gui's. -- robin - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html