Re: [PATCH] Documentation/fetch-options.txt: order options alphabetically
- From
Nanako Shiraishi <nanako3@lavabit.com>
- Date
- Oct 22, 2009, 10:21 UTC
- Message-ID
- <20091022192152.6117@nanako3.lavabit.com>
- In-Reply-To
- <7vhbts3285.fsf@alter.siamese.dyndns.org>
Quoting Junio C Hamano <gitster@pobox.com>
> 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}Can't we introduce subsections in the OPTIONS section to group them together, like this (sorry, not a patch)?
OPTIONS -------
Options related to merging <---- added ~~~~~~~~~~~~~~~~~~~~~~~~~~ <---- added include::merge-options.txt[]
:git-pull: 1
--rebase:: Instead of a merge, perform a rebase after fetching. If there is a remote ref for the upstream branch, and this branch was rebased since last fetched, the rebase uses that information to avoid rebasing non-local changes. To make this the default for branch `<name>`, set configuration `branch.<name>.rebase` to `true`. + [NOTE] This is a potentially _dangerous_ mode of operation. It rewrites history, which does not bode well when you published that history already. Do *not* use this option unless you have read linkgit:git-rebase[1] carefully.
--no-rebase:: Override earlier --rebase.
Options related to fetching <---- added ~~~~~~~~~~~~~~~~~~~~~~~~~~~ <---- added include::fetch-options.txt[]
include::pull-fetch-param.txt[]
-- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/