From: Andreas Schwab <schwab@linux-m68k.org>
To: Tomi Belan <tomi.belan@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug: wrong documentation for git-fast-import's option command
Date: Sun, 30 Apr 2017 12:21:42 +0200 [thread overview]
Message-ID: <874lx68abt.fsf@linux-m68k.org> (raw)
In-Reply-To: <CACUV5oeKoVdncK3RjtusiqrACj1xLiS--z8vC+Rsvy5TF09Lsw@mail.gmail.com> (Tomi Belan's message of "Sun, 30 Apr 2017 02:07:47 +0200")
On Apr 30 2017, Tomi Belan <tomi.belan@gmail.com> wrote:
> The man page of git-fast-import says the syntax is "'option' SP
> <option> LF". But this is wrong, and commands like that will be
> silently ignored.
Unless <option> starts with 'git', as you have seen. Other importers
may recognize other options, eg 'option hg ...'.
> The correct syntax is e.g. "option git stats" or "option git
> big-file-threshold=123". The docs should say "'option' SP 'git' SP
> <option> LF" or maybe even "'option' SP 'git' SP <option> ('='
> <argument>)? LF" (similarly to the docs for feature), and explain this
> is meant to allow other consumers of the fast import format.
>
> Looks like this bug existed since the option command was added in
> 9c8398f in 2009. Am I the first one who tried to use it? ;-)
>
> Cheers,
>
> Tomi
>
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-04-30 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 0:07 Bug: wrong documentation for git-fast-import's option command Tomi Belan
2017-04-30 10:21 ` Andreas Schwab [this message]
2017-05-01 13:26 ` Tomi Belan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lx68abt.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=tomi.belan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.