Re: [PATCH v4 0/1] Documentation/git-sparse-checkout.txt: add an OPTIONS section
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 18, 2022, 16:30 UTC
- Message-ID
- <xmqqmthnb4uq.fsf@gitster.g>
- In-Reply-To
- <20220317123718.480093-1-shaoxuan.yuan02@gmail.com>
Shaoxuan Yuan <shaoxuan.yuan02@gmail.com> writes:
Show 21 quoted lines
> == 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).