From: David Miller <davem@davemloft.net>
To: me@tobin.cc
Cc: markus.heiser@darmarit.de, linux-doc@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] docs: Convert alias and bridge to rst
Date: Thu, 19 Jul 2018 07:28:45 +0900 (KST) [thread overview]
Message-ID: <20180719.072845.739644123972982742.davem@davemloft.net> (raw)
In-Reply-To: <20180718032736.8000-1-me@tobin.cc>
From: "Tobin C. Harding" <me@tobin.cc>
Date: Wed, 18 Jul 2018 13:27:34 +1000
> Here is my first attempt at working on converting docs in
> Documentation/networking to rst format. I've picked a couple of trivial
> ones to start with. If there is anything extra I can do to make your
> life easier during documentation conversion please say. (Also if there
> is some reason that it would be preferable to _not_ embark on this task
> please say :)
>
> This set does not make any changes to the converted files apart from
> formatting.
...
> v2:
> - remove incorrect patch from set (changing 'Indices' indentation)
Series applied, thanks 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
prev parent reply other threads:[~2018-07-18 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 3:27 [PATCH net-next v2 0/2] docs: Convert alias and bridge to rst Tobin C. Harding
2018-07-18 3:27 ` [PATCH net-next v2 1/2] docs: networking: Convert alias.txt " Tobin C. Harding
2018-07-18 3:27 ` [PATCH net-next v2 2/2] docs: networking: Convert bridge.txt " Tobin C. Harding
2018-07-18 22:28 ` David Miller [this message]
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=20180719.072845.739644123972982742.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=me@tobin.cc \
--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).