From: Junio C Hamano <gitster@pobox.com>
To: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
Cc: derrickstolee@github.com, vdye@github.com, git@vger.kernel.org,
newren@gmail.com
Subject: Re: [PATCH v4 0/1] Documentation/git-sparse-checkout.txt: add an OPTIONS section
Date: Fri, 18 Mar 2022 09:30:37 -0700 [thread overview]
Message-ID: <xmqqmthnb4uq.fsf@gitster.g> (raw)
In-Reply-To: <20220317123718.480093-1-shaoxuan.yuan02@gmail.com> (Shaoxuan Yuan's message of "Thu, 17 Mar 2022 20:37:17 +0800")
Shaoxuan Yuan <shaoxuan.yuan02@gmail.com> writes:
> == Updates Log ==
>
> Changes since v3 (based on v3's single patch):
>
> * changes according to Derrick [1]
>
> == Overview ==
>
> Add an OPTIONS section to the manual and move the descriptions/explanations for
> these options from below COMMANDS to OPTIONS.
>
> [1] https://lore.kernel.org/git/307ac60d-b0a1-ea90-8118-a4e02b809102@github.com/
>
>
> Shaoxuan Yuan (1):
> Documentation/git-sparse-checkout.txt: add an OPTIONS section
>
> Documentation/git-sparse-checkout.txt | 44 +++++++++------------------
> 1 file changed, 15 insertions(+), 29 deletions(-)
>
> base-commit: eb129e532a7c58ea34afeec70b0e2e029c0d5fee
It is not very helpful to give the name of an object that is not
publicly available. Basing a patch on some topics in flight is
fine, but please clearly state what it is based on in a cover letter
(if the topic is a multi-patch series) or below the three-dash line
(if it is a single patch).
next prev parent reply other threads:[~2022-03-18 16:31 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
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 ` Junio C Hamano [this message]
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=xmqqmthnb4uq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=derrickstolee@github.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 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.