From: Jesper Juhl <jesper.juhl@gmail.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Documentation maintainer?
Date: Tue, 9 Aug 2005 14:26:33 +0200 [thread overview]
Message-ID: <9a87484905080905261885f044@mail.gmail.com> (raw)
In-Reply-To: <42F85491.5090407@drzeus.cx>
On 8/9/05, Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> Who should be cc:d for document additions? It's a brand new document,
> not updates to an existing one.
I don't think there's a central documentation maintainer as such.
I recently submitted a brand new document myself and added Andrew
Morton to CC since he's the overall 2.6 maintainer, and Andrew has
been kind enough to add my document to the -mm tree for starters.
Hopefully it'll then migrate onto mainline eventually.
> I sent it out without any cc at all
> (Subject: [PATCH] ISA DMA API documentation) which got some attention,
> but not from anyone with the possibility to commit it would seem.
>
> Rgds
> Pierre
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2005-08-09 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 7:00 Documentation maintainer? Pierre Ossman
2005-08-09 12:26 ` Jesper Juhl [this message]
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=9a87484905080905261885f044@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@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