mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Michael Still <mikal@stillhq.com>
Cc: tmolina@cablespeed.com, akpm@osdl.org,
	linux-kernel@n-dimensional.de, linux-kernel@vger.kernel.org
Subject: Re: Fixing 2.6.0's broken documentation references
Date: Sun, 28 Dec 2003 14:02:20 -0800	[thread overview]
Message-ID: <20031228140220.718f2e91.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0312282145070.18079-100000@diskbox.stillhq.com>

On Sun, 28 Dec 2003 21:48:57 +1100 (EST) Michael Still <mikal@stillhq.com> wrote:

| On Sat, 27 Dec 2003, Thomas Molina wrote:
| 
| > I agree that having a documentation maintainer would be a good idea.  Hans 
| > could volunteer or I could if no one else wants it.  Whoever does it 
| > though, needs some assurance that patches won't be dropped on the floor.
| 
| I would think that any such maintainer would also have to deal with 
| kernel-doc, and making sure all of those scripts work / don't produce 
| errors. I got a bunch of patches into the late 2.5 cycle to deal with 
| that, but someone needs to keep that stuff working.
| 
| I'm happy to keep playing with those scripts, if other people are happy 
| with that.
| 
| My point is that documentation is more complex than just keeping the 
| comments in the source pointing at the right places -- there is a bunch of 
| infrastructure there as well.
| 
| On the dropped patch front, I had a lot of success getting patches into 
| the kernel via the Trivial Patch Monkey. Given the menial nature of this 
| sort of work, wouldn't this best be done by the janitors and sending 
| patches to trivial?

I agree, using kernel-janitors or trivial patch monkey should be
sufficient and acceptable.

--
~Randy

  reply	other threads:[~2003-12-28 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-27 13:12 Hans Ulrich Niedermann
2003-12-28  0:08 ` Andrew Morton
2003-12-28  3:34   ` Thomas Molina
2003-12-28 10:48     ` Michael Still
2003-12-28 22:02       ` Randy.Dunlap [this message]
2004-01-08 18:36   ` Hans Ulrich Niedermann

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=20031228140220.718f2e91.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@n-dimensional.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikal@stillhq.com \
    --cc=tmolina@cablespeed.com \
    /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

Powered by JetHome