On Sat, Nov 10, 2012 at 12:02:12PM -0800, Junio C Hamano wrote: > Krzysztof Mazur <krzysiek@xxxxxxxxxxxx> writes: > > > Maybe we should just add that <paths> is an shortcut for <pathspec> > > and fix places where paths and pathspec are mixed or <path> is used as > > <pathspec>. > > We should unify uses of <paths> and <path> (the former should be > <path>... or something). Currently in most cases "<paths>..." is used ;) > > Some places you need to give exact path (iow, these places you > cannot use pathspec), while most other places pathspec > (i.e. matching pattern) is accepted. I know, thats why I added a note that "<path> is not always used for pathspec". > > The manual correctly updated will most likely to use both <path> and > <pathspec> appropriately. So we should always use "<path>" for exact path, and "<pathspec>" for pathspecs patterns as defined in gitglossary. I think it's better to avoid "<paths>" and always use "<path>..." or "<pathspec>...". Krzysiek -- 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