On Fri, 9 Nov 2007, Jon Smirl wrote: > > Should "git log" and "git log path" have two different command names? Do you think that would really help? We actually have people complaining about the numebr of git commands already. And the thing is, "git log" is actually what things like "gitk" use to visualize the history, and all *those* commands want the two different modes too! You want a "global history" view in gitk, but you also want a "file limited view". So having two different commands is actually what people absolutely DO NOT want. On the same note: several git commands have totally different fundamental behaviour based on arguments - in ways even more different than "git log". At least "git log" always shows a log, the arguments just change what *part* of the log they show. For example, think about "git checkout": you can use it to check out individual files and directories, but you can obviously use it to switch branches (and create them!) too. That's actually a much bigger difference than the different modes of "git log", but considering how many people have complained about "many different commands", I think people seem to be happier with commands that do somewhat related things just depending on the kinds of arguments they get. Linus - 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
