From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Simple question on the Kernel Janitors project.
Date: Mon, 09 Feb 2015 11:37:22 +0000 [thread overview]
Message-ID: <20150209113722.GE5206@mwanda> (raw)
In-Reply-To: <CAOgR63fYNyn7ZJ=5EEPiRXTXKr0qUTvsUj0MFFnu6f0K6V1Lgg@mail.gmail.com>
On Mon, Feb 09, 2015 at 11:55:27AM +0100, Bas Peters wrote:
> Hey everyone,
>
> I have a very simple question: Why should I CC my patches to Kernel Janitors?
It's maybe a good idea to do it for the first patch if you are not sure
it's correct. Julia and I do it because otherwise we were fixing the
same problems and maintainers were getting annoyed at the duplicates.
> Isn't it the responsibility of the maintainer to correct and merge
> patches?
To review and merge patches, yes.
> If so, what
> value does it add to CC the KJML as well? Do you maintain another
> branch that's merged
> into the kernel at every release?
No.
regards,
dan carpenter
next prev parent reply other threads:[~2015-02-09 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 10:55 Simple question on the Kernel Janitors project Bas Peters
2015-02-09 11:37 ` Dan Carpenter [this message]
2015-02-09 12:02 ` Julia Lawall
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=20150209113722.GE5206@mwanda \
--to=dan.carpenter@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox