From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Dag Brattli <dagb@fast.no>
Subject: Re: [RANT] Linux-IrDA status
Date: Tue, 7 Nov 2000 17:38:09 -0800 [thread overview]
Message-ID: <20001107173809.A24129@bougret.hpl.hp.com> (raw)
In-Reply-To: <20001107171401.A24041@bougret.hpl.hp.com> <3A08AB56.10BD5007@mandrakesoft.com>
In-Reply-To: <3A08AB56.10BD5007@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Tue, Nov 07, 2000 at 08:24:38PM -0500
On Tue, Nov 07, 2000 at 08:24:38PM -0500, Jeff Garzik wrote:
>
> Take a look at
> http://www.uwsg.iu.edu/hypermail/linux/kernel/9908.0/0669.html This
> happened with ISDN. Slightly different situation, but similar.
I'm familiar with that. The *BIG* difference is that Dag has
always sent his patch to Linus from the very start, when it was still
small, whereas ISDN did stay on their patch from a long time.
> IMHO Dag should send break up his patches into small chunks, and feed
> those to Linus, with an explanation of each chunk. That's what
> everybody else does... :)
If you can break up stuff that has accumulated over one year,
please tell me so. Most of the original patches have been lost in the
mist of time. We could send it file by file, but that would give some
interesting results ;-)
There is also a tradeoff between having the maintainer doing
the filtering to make sure that what's get checked in is safe and
getting junk in the kernel. With IrDA, Dag make sure to test and
integrate each patch before sending it to Linus, which of course make
bigger chunks. Also, some of the contribution on the IrDA mailing list
are big chunks of patches by themselves.
Anyway, Linus should read the Linux-IrDA mailing list if he
really want to keep up with the gory details ;-)
> Jeff
Ciao...
Jean
-
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-08 1:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 1:14 Jean Tourrilhes
[not found] ` <3A08AB56.10BD5007@mandrakesoft.com>
2000-11-08 1:38 ` Jean Tourrilhes [this message]
2000-11-08 8:12 ` Russell King
[not found] <Pine.LNX.4.10.10011072030070.15254-100000@penguin.transmeta.com>
2000-11-08 5:08 ` Michael Rothwell
2000-11-08 5:23 ` Linus Torvalds
2000-11-08 7:26 ` Linus Torvalds
2000-11-08 8:14 ` Russell King
2000-11-08 12:15 ` [RANT] Linux-IrDA status, " Dag Brattli
2000-11-10 21:24 ` Pavel Machek
2000-11-08 12:31 ` Michael Rothwell
[not found] <Pine.LNX.4.10.10011072027520.15254-100000@penguin.transmeta.com>
[not found] ` <200011081204.MAA68767@tepid.osl.fast.no>
2000-11-08 18:20 ` Jean Tourrilhes
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=20001107173809.A24129@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=dagb@fast.no \
--cc=jgarzik@mandrakesoft.com \
--cc=jt@hpl.hp.com \
--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®