From: "Tobin C. Harding" <me@tobin.cc>
To: "David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] docs: net: Convert netdev-FAQ to RST
Date: Wed, 25 Jul 2018 13:28:10 +1000 [thread overview]
Message-ID: <20180725032810.GA6067@eros> (raw)
In-Reply-To: <20180725025005.14332-1-me@tobin.cc>
On Wed, Jul 25, 2018 at 12:50:03PM +1000, Tobin C. Harding wrote:
Please drop this. I've forgotten to deal with the links from
Documentation/*.rst to Documentation/networking/netdev-FAQ.txt
Since I've already botched it can I ask for guidance here. The problem
is updating the links means making changes that will cause merge
conflicts if they go through net-dev tree (since most references are in
Documentation/*.rst). But we can't go through docs tree either since
that could lead to merge conflicts later as well.
My idea was to leave netdev-FAQ.txt in place but with all content
removed except
'This file has moved to netdev-FAQ.rst. This file will be removed once
netdev RST conversion is complete'
And then do the same for each file conversion under
Documentation/networking/. Once all the files are converted a single
patch set updating all references into Documentation/networking/*.rst
could be posted to the docs tree.
One other idea was to leave a symlink netdev-FAQ.txt -> netdev-FAQ.rst
but I don't know how that would play with the build system (docs or
otherwise).
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
WARNING: multiple messages have this Message-ID (diff)
From: "Tobin C. Harding" <me@tobin.cc>
To: "David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] docs: net: Convert netdev-FAQ to RST
Date: Wed, 25 Jul 2018 13:28:10 +1000 [thread overview]
Message-ID: <20180725032810.GA6067@eros> (raw)
In-Reply-To: <20180725025005.14332-1-me@tobin.cc>
On Wed, Jul 25, 2018 at 12:50:03PM +1000, Tobin C. Harding wrote:
Please drop this. I've forgotten to deal with the links from
Documentation/*.rst to Documentation/networking/netdev-FAQ.txt
Since I've already botched it can I ask for guidance here. The problem
is updating the links means making changes that will cause merge
conflicts if they go through net-dev tree (since most references are in
Documentation/*.rst). But we can't go through docs tree either since
that could lead to merge conflicts later as well.
My idea was to leave netdev-FAQ.txt in place but with all content
removed except
'This file has moved to netdev-FAQ.rst. This file will be removed once
netdev RST conversion is complete'
And then do the same for each file conversion under
Documentation/networking/. Once all the files are converted a single
patch set updating all references into Documentation/networking/*.rst
could be posted to the docs tree.
One other idea was to leave a symlink netdev-FAQ.txt -> netdev-FAQ.rst
but I don't know how that would play with the build system (docs or
otherwise).
thanks,
Tobin.
next prev parent reply other threads:[~2018-07-25 3:28 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
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 ` Tobin C. Harding [this message]
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 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=20180725032810.GA6067@eros \
--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 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.