From: "Ph. Marek" <philipp.marek@bmlv.gv.at>
To: Cal Peake <cp@absolutedigital.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] documentation fixes
Date: Wed, 1 Aug 2007 07:55:35 +0200 [thread overview]
Message-ID: <200708010755.36022.philipp.marek@bmlv.gv.at> (raw)
In-Reply-To: <Pine.LNX.4.64.0707311606350.13917@lancer.cnet.absolutedigital.net>
On Dienstag, 31. Juli 2007, Cal Peake wrote:
> > Whom should I CC for other documentation updates? Is the maintainer
> > the correct person, or are such small fixes "send and forget"?
>
> For spelling and grammar fixes, sending to trivial@kernel.org is prolly
> the best bet with a CC to l-k.
>
> Also, please see Documentation/SubmittingPatches, particularly section 12
> about signing off your work.
Ok, thank you!
Regards,
Phil
next prev parent reply other threads:[~2007-08-01 5:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 9:14 Ph. Marek
2007-07-31 20:14 ` Cal Peake
2007-08-01 5:55 ` Ph. Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-06 23:12 [PATCH] Documentation fixes Daniel Walker
2005-07-06 23:27 ` randy_dunlap
2004-12-23 23:09 Martin Waitz
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=200708010755.36022.philipp.marek@bmlv.gv.at \
--to=philipp.marek@bmlv.gv.at \
--cc=cp@absolutedigital.net \
--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
all inboxes | Powered by JetHome®