public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@convergence.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Michael Hunold <hunold@convergence.de>,
	linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Holger Waechtler <holger@convergence.de>
Subject: Re: DVB updates, 3rd try
Date: Wed, 18 Jun 2003 21:39:24 +0200	[thread overview]
Message-ID: <20030618193924.GA10511@convergence.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0306180849150.9782-100000@home.transmeta.com>

Hello Linus,

Linus Torvalds wrote:
> 
> I don't go out to fetch patches, I really want to see them come to me (and
> even then preferably through a few people acting as quality control and
> maintainership).
> 
> And if there is no clear maintainership relationship and you need to send
> them directly to me, I really want plain-text patches (they can be big if
> needed), with:

It would be great if we could clarfiy DVB maintainership. It would
nice to "appoint" one maintainer to whom we should send the
patches. If no one else volunteers, we will send them to you directly,
if you want with Cc: to lkml.

Alan Cox was the first one to merge the DVB subsystem into his 2.5 kernel
tree, but hinted that future updates should be sent in your direction.
Maybe that was just because he was busy with the IDE drivers, maybe
there are other reasons. I don't know.

The code base for the DVB drivers has grown over the last 3..4 years,
and there was a lot of stuff we wanted to clean up before inclusion in
the kernel. The pre-halloween merge was somewhat too soon, and there
were considerable cleanups afterwards which resulted in rather large
patches. Even after this current patch set, there is already a pile of
stuff to be merged. But the drivers in our CVS are already in a stable
condition, so future patches might be smaller ;-)


Thanks,
Johannes

      parent reply	other threads:[~2003-06-18 19:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 13:08 DVB updates, 2nd try Michael Hunold
2003-05-28 10:12 ` Christoph Hellwig
2003-05-28 12:54   ` Michael Hunold
2003-05-28 12:58     ` Christoph Hellwig
2003-06-18 11:49   ` DVB updates, 3rd try Michael Hunold
2003-06-18 15:58     ` Linus Torvalds
2003-06-18 16:12       ` John Levon
2003-06-19  1:45         ` jw schultz
2003-06-19  2:13           ` John Levon
2003-06-19  8:55             ` jw schultz
2003-06-18 19:39       ` Johannes Stezenbach [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=20030618193924.GA10511@convergence.de \
    --to=js@convergence.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hch@infradead.org \
    --cc=holger@convergence.de \
    --cc=hunold@convergence.de \
    --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