From: Jonathan Corbet <corbet@lwn.net>
To: "Héctor Orón Martínez" <hector.oron@gmail.com>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc: fix warnings for unused files in toctree
Date: Tue, 29 Oct 2019 05:01:23 -0600 [thread overview]
Message-ID: <20191029050123.54a474e6@lwn.net> (raw)
In-Reply-To: <CAODfWeF_xAhQJvRSBiDBQco8OG0kaH69eD=VbxBjB2fnPAXWnA@mail.gmail.com>
On Tue, 29 Oct 2019 11:58:21 +0100
Héctor Orón Martínez <hector.oron@gmail.com> wrote:
> > - Please work against docs-next and look at the history of what you are
> > working on. For example:
>
> Where do I find the docs-next tree?
It's in the MAINTAINERS file:
T: git git://git.lwn.net/linux.git docs-next
Thanks,
jon
next prev parent reply other threads:[~2019-10-29 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 17:12 [PATCH] doc: fix warnings for unused files in toctree Héctor Orón Martínez
2019-10-28 17:26 ` Héctor Orón Martínez
2019-10-29 9:21 ` Jonathan Corbet
2019-10-29 10:58 ` Héctor Orón Martínez
2019-10-29 11:01 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 13:44 hector.oron
2019-10-29 14:43 ` Jonathan Corbet
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=20191029050123.54a474e6@lwn.net \
--to=corbet@lwn.net \
--cc=hector.oron@gmail.com \
--cc=linux-doc@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).