From: "Tobin C. Harding" <me@tobin.cc>
To: Edward Cree <ecree@solarflare.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] docs: Add rest label the_canonical_path_format
Date: Thu, 26 Jul 2018 08:26:06 +1000 [thread overview]
Message-ID: <20180725222606.GC6067@eros> (raw)
In-Reply-To: <010bd587-6e4d-549e-e613-cb785f614463@solarflare.com>
On Wed, Jul 25, 2018 at 03:36:55PM +0100, Edward Cree wrote:
> On 25/07/18 03:50, Tobin C. Harding wrote:
> > 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'.
> Here and in the Subject, 'patch' is typoed as 'path'.
Thanks for the review Edward, will fix for next spin.
Tobin
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Tobin C. Harding" <me@tobin.cc>
To: Edward Cree <ecree@solarflare.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] docs: Add rest label the_canonical_path_format
Date: Thu, 26 Jul 2018 08:26:06 +1000 [thread overview]
Message-ID: <20180725222606.GC6067@eros> (raw)
In-Reply-To: <010bd587-6e4d-549e-e613-cb785f614463@solarflare.com>
On Wed, Jul 25, 2018 at 03:36:55PM +0100, Edward Cree wrote:
> On 25/07/18 03:50, Tobin C. Harding wrote:
> > 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'.
> Here and in the Subject, 'patch' is typoed as 'path'.
Thanks for the review Edward, will fix for next spin.
Tobin
next prev parent reply other threads:[~2018-07-25 22:26 UTC|newest]
Thread overview: 16+ 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
2018-07-25 2:50 ` [PATCH net-next 1/2] docs: Add rest label the_canonical_path_format Tobin C. Harding
2018-07-25 2:50 ` Tobin C. Harding
2018-07-25 14:36 ` Edward Cree
2018-07-25 14:36 ` Edward Cree
2018-07-25 22:26 ` Tobin C. Harding [this message]
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 2:50 ` 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 3:28 ` Tobin C. Harding
2018-07-25 14:14 ` Jonathan Corbet
2018-07-25 14:14 ` Jonathan Corbet
2018-07-25 22:31 ` Tobin C. Harding
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=20180725222606.GC6067@eros \
--to=me@tobin.cc \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--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 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.