From: Jonathan Corbet <corbet@lwn.net>
To: ksummit-discuss@lists.linux-foundation.org
Subject: [Ksummit-discuss] [MAINTAINERS SUMMIT] Documentation issues
Date: Fri, 23 Jun 2017 12:39:36 -0600 [thread overview]
Message-ID: <20170623123936.42dab05f@lwn.net> (raw)
The docs pull for 4.13 will include the conversion of the last DocBook
template files, thanks mostly to Mauro. That's the good news; the bad
news is that I get to explain a lot of merge conflicts to Linus, most of
which result from other trees reaching into Documentation/ and changing
files that have been converted.
I can continue in this mode, but I do wonder if there's a better way out
there somewhere. So I think there would be value in a session on the
maintenance of "subsystems" that don't fit neatly into the kernel
source-tree hierarchy.
We could also talk about the state of the RST conversion and whether/how
we'd like it to continue. Perhaps we would rather, as Peter recently
suggested, "just delete all that nonsense and go back to 80 column 7bit
ASCII"? In general, what do the maintainers want from the documentation
subsystem, and how can we make it easy to continue improving our docs?
jon
next reply other threads:[~2017-06-23 18:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 18:39 Jonathan Corbet [this message]
2017-06-23 23:09 ` [Ksummit-discuss] [MAINTAINERS SUMMIT] Documentation issues Rafael J. Wysocki
2017-06-24 12:03 ` Rafael J. Wysocki
2017-06-24 10:46 ` Mauro Carvalho Chehab
2017-06-24 12:20 ` Rafael J. Wysocki
2017-06-24 13:41 ` Mauro Carvalho Chehab
2017-06-25 20:56 ` Jiri Kosina
2017-06-26 1:20 ` Mauro Carvalho Chehab
2017-06-26 21:18 ` Rafael J. Wysocki
2017-06-26 5:58 ` Takashi Iwai
2017-06-26 21:28 ` Rafael J. Wysocki
2017-06-27 8:41 ` Daniel Vetter
2017-06-27 10:31 ` Mauro Carvalho Chehab
2017-06-26 22:18 ` Jonathan Corbet
2017-06-27 18:42 ` Bird, Timothy
2017-06-28 19:48 ` Geert Uytterhoeven
[not found] ` <CAFhKne8ZttmqWYJToCw9EDywzeMdp=eiFpoZ+O5xrzmKnpA09Q@mail.gmail.com>
[not found] ` <CAFhKne_W-EbjUd_Cm4kyBHrVK6K9r8Ss3gY0ogO1nztbQZYBEg@mail.gmail.com>
2017-06-25 21:32 ` Matthew Wilcox
2017-06-25 21:42 ` Rafael J. Wysocki
2017-06-26 1:15 ` Mauro Carvalho Chehab
2017-06-26 21:16 ` Rafael J. Wysocki
2017-06-26 0:58 ` Mauro Carvalho Chehab
2017-06-25 16:13 ` Jonathan Corbet
2017-06-26 12:19 ` Mark Brown
2017-06-27 8:38 ` Daniel Vetter
2017-06-27 15:33 ` Mark Brown
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=20170623123936.42dab05f@lwn.net \
--to=corbet@lwn.net \
--cc=ksummit-discuss@lists.linux-foundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).