Re: [PATCH v2 6/7] Documentation: put blame/log -L in sticked form

Junio C Hamano gits...@pobox.com writes: Thomas Rast t...@thomasrast.ch writes: The next patch will document gitk -L, but gitk does not understand the separated form ('gitk -L :foo:bar' results in an error). Spell git-blame and git-log -L, which are supposed to be the same option, without

Re: [PATCH v2 6/7] Documentation: put blame/log -L in sticked form

Thomas Rast t...@thomasrast.ch writes: Junio C Hamano gits...@pobox.com writes: Thomas Rast t...@thomasrast.ch writes: The next patch will document gitk -L, but gitk does not understand the separated form ('gitk -L :foo:bar' results in an error). Spell git-blame and git-log -L, which are

Re: [PATCH v2 6/7] Documentation: put blame/log -L in sticked form

Junio C Hamano gits...@pobox.com writes: Thomas Rast t...@thomasrast.ch writes: Junio C Hamano gits...@pobox.com writes: I agree that this patch may reduce confusion locally, but if we were to go in this direction, we should be consistent and enforce stuck form everywhere, Hmm. Do you

Re: [PATCH v2 6/7] Documentation: put blame/log -L in sticked form

Thomas Rast t...@thomasrast.ch writes: So my short-term plan just became: document instead of fix; clean up manpages towards the stuck form for long options; have gitk only parse -Lstuck. Medium term we can move gitk to a different option parser, resolving at least that inconsistency.

Re: [PATCH v2 6/7] Documentation: put blame/log -L in sticked form

Thomas Rast t...@thomasrast.ch writes: The next patch will document gitk -L, but gitk does not understand the separated form ('gitk -L :foo:bar' results in an error). Spell git-blame and git-log -L, which are supposed to be the same option, without the spaces to prevent confusion. I agree