From: Junio C Hamano <gitster@pobox.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: [PATCH] SubmittingPatches: add section for iterating patches
Date: Fri, 17 May 2024 10:23:40 -0700 [thread overview]
Message-ID: <xmqq8r08jqsj.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZS1bhHAtz59z71sMxOT63jwF0pHYO5YKtY7Lx_V8ubV4A@mail.gmail.com> (Karthik Nayak's message of "Fri, 17 May 2024 11:33:42 +0000")
Karthik Nayak <karthik.188@gmail.com> writes:
>>> +. Build on a suitable base branch, see the <<choose-starting-point, section above>>,
>>> +and format-patch the series. If you are doing "rebase -i" in-place to
>>> +update from the previous round, this will reuse the previous base so
>>> +(2) and (3) may become trivial.
>>> +
>>> +. Find the base of where the last round was queued
>>
>> It's somewhat unusual for bulleted lists to start with a dot, but this
>> is consistent with the remainder of this document.
>
> Yeah, that's mostly why I added dots instead of asterisks here.
Here we want a list of numbered items so that we can refer to other
items in the same list like "(2) and (3) may become trivial".
Wouldn't asterisks give us an unordered list that is typically
rendered as a list of unordered items instead?
next prev parent reply other threads:[~2024-05-17 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 12:30 [PATCH] SubmittingPatches: add section for iterating patches Karthik Nayak
2024-05-17 5:15 ` Patrick Steinhardt
2024-05-17 11:33 ` Karthik Nayak
2024-05-17 17:23 ` Junio C Hamano [this message]
2024-05-21 6:17 ` Patrick Steinhardt
2024-05-17 12:27 ` [PATCH v2] " Karthik Nayak
2024-05-17 17:24 ` Junio C Hamano
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=xmqq8r08jqsj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).