From: "Drew DeVault" <sir@cmpwn.com>
To: "Jani Nikula" <jani.nikula@linux.intel.com>,
<linux-doc@vger.kernel.org>, "Jonathan Corbet" <corbet@lwn.net>
Cc: "Drew DeVault" <sir@cmpwn.com>
Subject: Re: [PATCH] submitting-patches.rst: streamline for git usage
Date: Fri, 28 Aug 2020 08:31:00 -0400 [thread overview]
Message-ID: <C58MQIQSGGUI.1I8IVCR8DPW0C@homura> (raw)
In-Reply-To: <87y2lz3xwe.fsf@intel.com>
On Fri Aug 28, 2020 at 5:47 AM EDT, Jani Nikula wrote:
> > -2) Describe your changes
> > +1) Describe your changes
> > ------------------------
>
> I suggest just tossing the numbering altoghether while at it.
Because there are so many headings, I think the numbering is still
useful for being able to easily refer to a specific step when asking
questions.
next prev parent reply other threads:[~2020-08-28 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 17:42 [PATCH] submitting-patches.rst: streamline for git usage Drew DeVault
2020-08-28 9:47 ` Jani Nikula
2020-08-28 12:31 ` Drew DeVault [this message]
2020-08-31 7:13 ` Jani Nikula
2020-08-31 22:26 ` Jonathan Corbet
2020-08-31 23:01 ` Drew DeVault
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=C58MQIQSGGUI.1I8IVCR8DPW0C@homura \
--to=sir@cmpwn.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
/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