Wincent Colaiuta <win@xxxxxxxxxxx> writes: > I think if you're introducing a different command then you should make > sure it doesn't happen to be an abbreviation of an existing one. It > would be better to give it some other name (info, foo, whatever). If > svn people then want to make an "st" alias pointing to it they're free > to do so. In Subversion and Bazaar "info" command gives mostly information about the repository itself. They don't talk about individual files at all. "status" is the command (also in Mercurial) for getting information about the current state of files in the tree. I think it would be really sad if "git status" can't be extended to match people's needs. I don't like the idea of a new name for such status command. It's a kind of "why git people always invent new names for familiar commands?" thing. -- 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
