From: Jani Nikula <jani.nikula@linux.intel.com>
To: Drew DeVault <sir@cmpwn.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 12:47:13 +0300 [thread overview]
Message-ID: <87y2lz3xwe.fsf@intel.com> (raw)
In-Reply-To: <20200827174237.121004-1-sir@cmpwn.com>
On Thu, 27 Aug 2020, Drew DeVault <sir@cmpwn.com> wrote:
> This document is a bit intimidating to new patch submitters, and this
> change streamlines it a bit. We presume git usage, because it's much
> easier to use and most devs coming at the kernel are likely to be
> familiar with it.
...and those who deviate from git should know what they're doing without
this.
> -2) Describe your changes
> +1) Describe your changes
> ------------------------
I suggest just tossing the numbering altoghether while at it.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2020-08-28 9:47 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 [this message]
2020-08-28 12:31 ` Drew DeVault
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=87y2lz3xwe.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=sir@cmpwn.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.