From: Tomi Belan <tomi.belan@gmail.com>
Date: Mon, 01 May 2017 13:26:30 GMT
Subject: Re: Bug: wrong documentation for git-fast-import's option command
Message-ID: <CACUV5ocdADaXYpcQG6kJ0CaR+d+EwyaSFFReaO2ni+1CnJMvyw@mail.gmail.com>
In-Reply-To: <874lx68abt.fsf@linux-m68k.org>

On Sun, Apr 30, 2017 at 12:21 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Unless <option> starts with 'git', as you have seen.  Other importers
> may recognize other options, eg 'option hg ...'.

Hmm? Are you disagreeing with how I described the issue, or saying
there is no issue at all? I'm not sure.

I know the syntax is meant for other importers, which might accept
different options. My point is that the man page doesn't say anything
about that. If a frontend follows the man page and just prints e.g.
"option quiet", git-fast-import will silently ignore it.

If you dislike my suggested fix "'option' SP 'git' SP ...", then how about
'option' SP <program> SP <option> ('=' <argument>)? LF
and saying that for options supported by Git, <program> must be 'git'?

Cheers,

Tomi