From: Jonathan Corbet <corbet@lwn.net>
To: linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, Randy Dunlap <randy.dunlap@oracle.com>
Subject: [Pull] Some documentation patches
Date: Fri, 28 Mar 2008 12:20:12 -0600 [thread overview]
Message-ID: <13387.1206728412@vena.lwn.net> (raw)
I've noticed that getting documentation patches merged seems to be a
slower and more uncertain process than it was a while back. So I
figured I'd try to be one of the cool folks with their own git tree and
see if that works better. Linus, if you agree, could you please pull:
git://git.lwn.net/linux-2.6.git docs
To get the following:
Jonathan Corbet (3):
Add the seq_file documentation
Fill out information on patch tags in SubmittingPatches
Add a comment discouraging use of in_atomic()
Documentation/SubmittingPatches | 54 ++++++-
Documentation/filesystems/00-INDEX | 2 +
Documentation/filesystems/seq_file.txt | 283 ++++++++++++++++++++++++++++++++
include/linux/hardirq.h | 8 +
4 files changed, 344 insertions(+), 3 deletions(-)
create mode 100644 Documentation/filesystems/seq_file.txt
These changes are (1) an updated version of the seq_file document first
posted in 2003, (2) the much-reviewed patch tags documentation, and
(3) a comment warning developers that in_atomic() doesn't mean what they
think it means. No code changes.
If this works out, and nobody objects, I'll try to run this tree into
the future as a collection point for documentation patches which don't
have a more obvious tree to travel through.
Thanks,
jon
next reply other threads:[~2008-03-28 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 18:20 Jonathan Corbet [this message]
2008-03-28 18:28 ` [Pull] Some documentation patches Jan Engelhardt
2008-03-28 18:34 ` Linus Torvalds
2008-03-28 18:36 ` Jonathan Corbet
2008-03-28 19:09 ` Jan Engelhardt
2008-03-28 19:22 ` Jonathan Corbet
2008-03-31 14:31 ` Dmitri Vorobiev
2008-04-01 20:00 ` Jan Engelhardt
2008-03-28 19:39 ` Will Newton
2008-03-28 19:47 ` Randy Dunlap
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=13387.1206728412@vena.lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@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