Thomas Rast 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.
>
> Longer term we
Junio C Hamano writes:
> Thomas Rast writes:
>
>> Junio C Hamano 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 want to go there?
>
> Absolutely
Thomas Rast writes:
> Junio C Hamano writes:
>
>> Thomas Rast 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,
>>> w
Junio C Hamano writes:
> Thomas Rast 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 co
Thomas Rast 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 that this patc
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.
Signed-off-by: Thomas Rast
---
Documentation/blame
6 matches
Mail list logo