From: Arjan van de Ven <arjan@infradead.org>
To: Ben Collins <ben.collins@ubuntu.com>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH]: How to be a kernel driver maintainer
Date: Sun, 08 Jan 2006 19:43:58 +0100 [thread overview]
Message-ID: <1136745838.2955.17.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1136744870.1043.4.camel@grayson>
> But this isn't at al true. Almost all subsystems maintain the primary
> tree outside of the kernel, with the kernel being the primary _stable_
> tree. USB, Netdev,
patches yes. but usually only small stuff
> Alsa, etc. All changes go someplace else before being
> pushed to the primary kernel tree. 99% of the time, patches are going
> somewhere else before going into the main kernel.
that's different... that's a patch queue. That's not the same as being
the prime repository.
> So the above
> paragraphs is really misleading.
I guess neither is good then. I certainly would absolutely not want to
encourage developers to have a main "real driver" outside the kernel
source. Linus calls that "the cvs mentality" and time after time that
has proven to be really bad. You mention alsa, and to some degree alsa
is suffering from this ;(
(this is different from net/usb/scsi where changes are queued but merged
regularly and near immediately in case of bugfixes, unlike things like
alsa and firewire where basically the only choice is "all or nothing"
where "all" is bugfixes and new bugs)
next prev parent reply other threads:[~2006-01-08 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 16:07 Ben Collins
2006-01-08 16:33 ` Arjan van de Ven
2006-01-08 18:27 ` Ben Collins
2006-01-08 18:43 ` Arjan van de Ven [this message]
2006-01-08 18:57 ` Arjan van de Ven
2006-01-09 9:51 ` Joel Becker
2006-01-08 21:45 ` [PATCH updated]: " Ben Collins
2006-01-09 7:46 ` Arjan van de Ven
2006-01-09 13:34 ` Ben Collins
2006-01-09 14:02 ` Grant Coady
2006-01-09 21:28 ` Arjan van de Ven
2006-01-10 0:09 ` Linus Torvalds
2006-01-10 0:58 ` Ben Collins
2006-03-08 18:03 ` [Updated]: How to become " Ben Collins
2006-03-08 19:05 ` Jesper Juhl
2006-03-08 19:10 ` Arjan van de Ven
2006-03-08 19:27 ` Jesper Juhl
2006-06-02 21:38 ` [Updated v3]: " Ben Collins
2006-06-02 22:16 ` Randy.Dunlap
2006-06-03 0:03 ` Greg KH
2006-06-05 10:27 ` Jan Engelhardt
2006-03-09 4:32 ` [Updated]: " Randy.Dunlap
2006-01-08 21:47 ` [PATCH]: How to be " Ben Collins
2006-01-09 19:26 ` Pavel Machek
2006-01-10 15:10 ` Ben Collins
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=1136745838.2955.17.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=ben.collins@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®