From: Derrick Stolee <derrickstolee@github.com>
To: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>, git@vger.kernel.org
Cc: vdye@github.com, newren@gmail.com, bagasdotme@gmail.com
Subject: Re: [RFC PATCH 1/1] Documentation/git-sparse-checkout.txt: add an OPTIONS section
Date: Fri, 11 Mar 2022 15:56:41 -0500 [thread overview]
Message-ID: <dd9413da-1b8c-2adf-c471-e5fd4230375c@github.com> (raw)
In-Reply-To: <20220311132141.1817-2-shaoxuan.yuan02@gmail.com>
On 3/11/2022 8:21 AM, Shaoxuan Yuan wrote:
> Add an OPTIONS section to the manual and move the descriptions about
> these options from COMMANDS to the section.
This is a good goal.
> +OPTIONS
> +-------
However, there are a few issues with the current approach. First, I
believe it would be better to start with COMMANDS, then OPTIONS.
To be fair, we are not consistent here. These commands use OPTIONS
and then COMMANDS:
* git-commit-graph.txt
* git-remote.txt
* git-revert.txt
These use [SUB]COMMANDS and then OPTIONS:
* git-maintenance.txt
* git-notes.txt
* git-p4.txt
* git-stash.txt
* git-submodule.txt
* git-worktree.txt
My preference would be OPTIONS second (and we can clean up the
other docs as #leftoverbits). In particular, I noticed that
the SYNOPSIS for git-maintenance.txt is out of date.
> +'--[no-]cone'::
> + Use with ['set'|'reapply'].
> + Specify using cone mode or not. The default is to use cone mode.
> +
> By default, the input list is considered a list of directories, matching
> the output of `git ls-tree -d --name-only`. This includes interpreting
The other issue is that this context is detailing information about
the 'set' command and the input it takes. You'll want to make sure
the information is properly grouped.
> @@ -78,6 +59,11 @@ with the `--sparse-index` option, and will likely be incompatible with
> other new features as they are added. See the "Non-cone Problems"
> section below and the "Sparse Checkout" section of
> linkgit:git-read-tree[1] for more details.
> +
> +'--[no-]sparse-index'::
> + Use with ['set'|'reapply'].
I do like these clear indicators of which commands allow this
option. I wonder if it should instead be
Use with the `set` and `reapply` commands.
Thanks,
-Stolee
next prev parent reply other threads:[~2022-03-11 20:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 13:21 [RFC PATCH 0/1] Documentation/git-sparse-checkout.txt: add an OPTIONS section Shaoxuan Yuan
2022-03-11 13:21 ` [RFC PATCH 1/1] " Shaoxuan Yuan
2022-03-11 20:56 ` Derrick Stolee [this message]
2022-03-14 6:34 ` [PATCH v2 0/1] " Shaoxuan Yuan
2022-03-14 6:34 ` [PATCH v2 1/1] " Shaoxuan Yuan
2022-03-14 6:56 ` [PATCH v3 0/1] " Shaoxuan Yuan
2022-03-14 6:56 ` [PATCH v3 1/1] " Shaoxuan Yuan
2022-03-14 16:13 ` Derrick Stolee
2022-03-17 12:37 ` [PATCH v4 0/1] " Shaoxuan Yuan
2022-03-17 12:37 ` [PATCH v4 1/1] " Shaoxuan Yuan
2022-03-18 16:47 ` Junio C Hamano
2022-03-18 16:30 ` [PATCH v4 0/1] " Junio C Hamano
2022-03-19 6:19 ` [PATCH v5 0/4] " Shaoxuan Yuan
2022-03-19 6:19 ` [PATCH v5 1/4] " Shaoxuan Yuan
2022-03-19 6:19 ` [PATCH v5 2/4] Documentation/git-sparse-checkout.txt: move OPTIONS after COMMANDS Shaoxuan Yuan
2022-03-19 6:19 ` [PATCH v5 3/4] Documentation/git-sparse-checkout.txt: some reword and modifications Shaoxuan Yuan
2022-03-19 6:19 ` [PATCH v5 4/4] " Shaoxuan Yuan
2022-03-22 15:05 ` [PATCH v5 0/4] Documentation/git-sparse-checkout.txt: add an OPTIONS section Derrick Stolee
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=dd9413da-1b8c-2adf-c471-e5fd4230375c@github.com \
--to=derrickstolee@github.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=shaoxuan.yuan02@gmail.com \
--cc=vdye@github.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).