From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [faq patch] mail per subsystem
Date: Mon, 11 Jul 2005 05:36:18 +0000 [thread overview]
Message-ID: <20050711053618.GA14070@us.ibm.com> (raw)
In-Reply-To: <20050707093332.GA21414@nd47.coderock.org>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On 07.07.2005 [11:33:32 +0200], Domen Puncer wrote:
> Hi!
>
> nacc noted on irc, that this is not in faq, but probably should be.
> Here's a compact version I came up with:
>
> Comments? Better wordings?
Patch makes sense; here's one with one grammatical fix & a link to the
conversation with David Miller on LKML.
Thanks,
Nish
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
--- faq 2005-07-10 22:34:38.000000000 -0700
+++ faq.dev 2005-07-10 22:34:30.000000000 -0700
@@ -24,6 +24,13 @@ Q: Where should I send patches to?
A: Mailing list: kernel-janitors@lists.osdl.org
If you feel confident enough, you can CC: someone from MAINTAINERS too.
+Q: I have lots of patches that do the same thing. Can I just send them in
+ one mail?
+A: No, but don't send them in lots of small mails either. Try splitting
+ them up per subsystem (drivers/net/, fs/ext3/...). See here:
+ http://marc.theaimsgroup.com/?l=linux-kernel&m=112105809816217&w=2
+ for details.
+
Q: Where can I find janitors?
A: On our mailing list and #kerneljanitor at irc.oftc.net
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-07-11 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 9:33 [KJ] [faq patch] mail per subsystem Domen Puncer
2005-07-11 5:36 ` Nishanth Aravamudan [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=20050711053618.GA14070@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.