On Mon, May 15, 2006 at 10:29:20AM -0600, Eric W. Biederman wrote: > Sure. If it gets included in a tutorial is great, but existing > users aren't likely to read through a tutorial if they think they > know what is going on. > > Having it documented in the man pages (i.e. the reference > documentation) which is where people look to check up on the fine > points of a command is more likely to matter. Looks like the current git-log man page refers you to the git-rev-list page for that, and the use of path names is documented there. I think that's a pretty reasonable approach for reference documentation, which should be concise. Duplicating the git-rev-list documentation (even some of it) to every man page to which it's relevant would add a lot of text. The current git-log man page is misleading, though--it suggests that git-log accepts (and git-rev-list documents) only options, which might discourage a reader from tracking down information about non-option arguments. I also agree about the tutorial--the "Keeping track of history" section would be a good place to introduce this and git-grep with some fun examples. It's on my todo list, but may take a while, so maybe someone else can beat me to it.... --b. - 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 Tue May 16 03:56:31 2006
This archive was generated by hypermail 2.1.8 : 2006-05-16 03:56:49 EST