From: "Tobin C. Harding" <me@tobin.cc>
To: "David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <me@tobin.cc>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 1/2] docs: Add rest label the_canonical_path_format
Date: Wed, 25 Jul 2018 12:50:04 +1000 [thread overview]
Message-ID: <20180725025005.14332-2-me@tobin.cc> (raw)
In-Reply-To: <20180725025005.14332-1-me@tobin.cc>
In preparation to convert Documentation/network/netdev-FAQ.rst to
restructured text format we would like to be able to reference 'the
canonical patch format' section.
Add rest label: 'the_canonical_path_format'.
Signed-off-by: Tobin C. Harding <me@tobin.cc>
---
Documentation/process/submitting-patches.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index 908bb55be407..c0917107b90a 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -611,6 +611,7 @@ which stable kernel versions should receive your fix. This is the preferred
method for indicating a bug fixed by the patch. See :ref:`describe_changes`
for more details.
+.. _the_canonical_patch_format:
14) The canonical patch format
------------------------------
--
2.17.1
next prev parent reply other threads:[~2018-07-25 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 2:50 [PATCH net-next 0/2] docs: net: Convert netdev-FAQ to RST Tobin C. Harding
2018-07-25 2:50 ` Tobin C. Harding [this message]
2018-07-25 14:36 ` [PATCH net-next 1/2] docs: Add rest label the_canonical_path_format Edward Cree
2018-07-25 22:26 ` Tobin C. Harding
2018-07-25 2:50 ` [PATCH net-next 2/2] docs: net: Convert netdev-FAQ to restructured text Tobin C. Harding
2018-07-25 3:28 ` [PATCH net-next 0/2] docs: net: Convert netdev-FAQ to RST Tobin C. Harding
2018-07-25 14:14 ` Jonathan Corbet
2018-07-25 22:31 ` Tobin C. Harding
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=20180725025005.14332-2-me@tobin.cc \
--to=me@tobin.cc \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).