Re: [PATCH] Documentation/fetch-options.txt: order options alphabetically

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 21, 2009, 20:45 UTC
Message-ID: <7vhbts3285.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7vpr8g32ht.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 14 quoted lines

> Jari Aalto <jari.aalto@cante.net> writes:
>
>> Signed-off-by: Jari Aalto <jari.aalto@cante.net>
>> ---
>>  Documentation/fetch-options.txt |   48 +++++++++++++++++++-------------------
>>  1 files changed, 24 insertions(+), 24 deletions(-)
>
> Does this even make sense when git-pull.txt itself includes files other
> than this one?  fetch-options.txt may begin with the description of -a
> that is very early in the alphabetical sequence, but git-pull.txt includes
> merge-options.txt before this file, whose contents would describe what
> probably would come after -a (I didn't check).  Also git-pull.txt itself
> has description of --rebase and --no-rebase that definitely come before -a
> (I did check).

Ah, in your defense ;-) I think you looked only at git-fetch.txt without checking where else this file is included. Then the patch certainly is understandable. It would probably make git-fetch.{1,html} easier to scan, while making things not worse for git-pull.{1,html}