From: Lars Hanisch <dvb@cinnamon-sage.de>
To: linux-media@vger.kernel.org
Subject: Re: [linux-dvb] Cross-posting linux-media, linux-dvb etc
Date: Tue, 20 Jan 2009 19:21:08 +0100 [thread overview]
Message-ID: <49761614.2060708@cinnamon-sage.de> (raw)
In-Reply-To: <412bdbff0901200724v1c981f45te3558256571597a6@mail.gmail.com>
Devin Heitmueller wrote:
> People "in favor" of the lists being merged
> 118 Patrick Boettcher
> 205 Hans Verkuil
> 38 Mike Isely
> 196 Devin Heitmueller
> "hundreds" Mauro Carvalho Chehab
>
> People "against" of the lists being merged
> 2 Lars Hanisch
> 17 user.vdr
> 16 Klaus Schmidinger
> 2 Bob Cunningham
> 10 Tomas Drajsajtl
> 17 Ales Jurik
Just for the records: I'm "in favor" of the merge, not against... Or
have I missunderstood the post I replied to? Never mind. :)
> Yup, it's the developers who are posting on a regular basis who feel
> the pain of the two different lists. It's the people who are actively
> replying to issues, dealing with problems, and trying to keep track of
> it all who want the lists merged. That said, I personally don't feel
> any guilt in inconveniencing a few users who are not contributing if
> it makes it easier for the people who contribute to the list on a
> daily basis.
I'm a "user-only" of my PVR150/350 since about 2 years and I read
these lists (ivtv-devel, ivtv-users, video4linux, and now linux-media)
because I want to stay in touch with the really good work you developers
are doing (also a "Thank you" from my wife, who loves our VDR). And I
want to know when some of the issues I encounter are solved, so I can
update my kernel. Sadly I haven't the time to invest my
development-knowledge into linux-driver-development (my daily work is
application-development, and yes, it's windows, shame on me ;-)).
So, if the lists get merged or not, I still will be reading them. I
just want to give a view from a passive reader. And from that point of
view a merge would be fine...
But I agree that the main developers should be the ones that have the
final stay on this.
Lars.
next prev parent reply other threads:[~2009-01-20 18:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 14:48 Cross-posting linux-media, linux-dvb etc Patrick Boettcher
2009-01-16 14:55 ` [linux-dvb] " Hans Verkuil
2009-01-16 15:04 ` Mike Isely
2009-01-16 15:52 ` Benny Amorsen
2009-01-16 16:08 ` Luca Tettamanti
2009-01-21 2:40 ` Rick
2009-01-16 17:13 ` Lars Hanisch
2009-01-16 17:59 ` Mauro Carvalho Chehab
2009-01-16 18:01 ` Mauro Carvalho Chehab
2009-01-19 21:46 ` Bob Cunningham
2009-01-19 21:53 ` Devin Heitmueller
2009-01-19 22:47 ` Mauro Carvalho Chehab
2009-01-20 8:35 ` Tomas Drajsajtl
2009-01-20 8:56 ` Ales Jurik
2009-01-20 15:24 ` Devin Heitmueller
2009-01-20 16:00 ` Tomas Drajsajtl
2009-01-20 16:41 ` Steven Toth
2009-01-20 17:46 ` Mike Isely
2009-01-20 18:21 ` Lars Hanisch [this message]
2009-01-20 20:06 ` Andy Walls
2009-01-20 21:05 ` Mauro Carvalho Chehab
2009-01-20 21:20 ` Bob Cunningham
[not found] ` <af2e95fa0901210008y758a7bfai4e326d1f74cc7441@mail.gmail.com>
2009-01-21 8:09 ` [linux-dvb] Fwd: " Henrik Beckman
2009-01-16 23:29 ` [linux-dvb] " BOUWSMA Barry
2009-01-17 5:51 ` user.vdr
2009-01-17 6:03 ` Mike Isely
2009-01-17 9:36 ` BOUWSMA Barry
2009-01-18 9:53 ` [linux-media] " Klaus Schmidinger
2009-01-19 0:11 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 22:47 stev391
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=49761614.2060708@cinnamon-sage.de \
--to=dvb@cinnamon-sage.de \
--cc=linux-media@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