From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: RFC: "SubmittingPatches" text
Date: Sat, 18 Nov 2000 11:16:15 +0100 (MET) [thread overview]
Message-ID: <200011181016.LAA12939@cave.bitwizard.nl> (raw)
In-Reply-To: <E13wX8W-0008Qt-00@the-village.bc.nu> from Alan Cox at "Nov 16, 2000 10:04:02 pm"
Alan Cox wrote:
> Maybe also note that maintainers of given modules are much more likely to
> give feedback than Linus, also the [PATCH]: convention
Question:
Should a submitter CC Linus or linux-kernel on the patch before having
gotten approval from a maintainer?
I'd say DO CC Linux-kernel, don't CC Linus.
Otherwise Linus may get a patch that he doesn't know if it violates
the essential ideas behind some vague driver. And the message with it
could say: "As suggested by <driver-author>".
If Linux-kernel and the driver-author don't have any objections to the
patch, send it to Linus and the driver author, keeping Linux-kernel
out of the loop, this time with a note:
"Linus: Reviewed by <driver-author> and Linux-kernel,
please apply".
Note that Linus will not have read the previous discussion, so some of
the ideas of the patch may have to be repeated....
This is the way I'd like things to work. Feel free to disagree, and
try to convince me why it's wrong....
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* Common sense is the collection of *
****** prejudices acquired by age eighteen. -- Albert Einstein ********
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-18 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 21:32 RFC: "SubmittingPatches" text Jeff Garzik
2000-11-16 22:04 ` Alan Cox
2000-11-16 22:31 ` Tigran Aivazian
2000-11-17 2:22 ` Gary Lawrence Murphy
2000-11-18 10:16 ` Rogier Wolff [this message]
2000-11-18 13:36 ` Werner Almesberger
2000-11-17 4:59 ` Peter Samuelson
2000-11-17 8:30 ` Kai Germaschewski
2000-11-17 15:37 ` Andries Brouwer
2000-11-18 10:24 ` Rogier Wolff
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=200011181016.LAA12939@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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