From: Douglas Schilling Landgraf <dougsland@gmail.com>
To: "Markus Rechberger" <mrechberger@gmail.com>
Cc: Michael Krufky <mkrufky@linuxtv.org>, linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] [ANNOUNCE] DVB API improvements End-user point of view
Date: Thu, 25 Sep 2008 21:58:06 -0400 [thread overview]
Message-ID: <20080925215806.0bb585a3@gmail.com> (raw)
In-Reply-To: <d9def9db0809252150t9dd113axa9acd3d7c3817cb8@mail.gmail.com>
Hello,
On Fri, 26 Sep 2008 06:50:07 +0200
"Markus Rechberger" <mrechberger@gmail.com> wrote:
> permanent development for the last couple of months.
> All you could do there is to take out the usbids copy it to
> linuxtv.org and play against all the people
> who contributed to the other tree and which is manufacturer supported.
>
> I'd really better think twice if you want to keep up reverse
> engineered drivers with linux which are capable
> of melting devices (this happens with wrong configurations).
>
> Why am I interested in DVB? Because we have devices supporting
> multiple standards which are yet
> not directly supported by the DVB framework.
IMO, since I start in v4l/dvb you are always interested in create new
flame wars. Sorry my sincerely.
If you are really interested about v4l/dvb users why I don't see you in
plumbers conference to understand your point of view and discuss with
API is better?
> The lies that I forked off the driver which I initially submitted to
> linuxtv is ridiculous as you modified the wiki
> site on linuxtv.org. See all that you and Mauro basically have done is
> copying the code from mcentral.de
Yes, "always copying your forked and GPL code".
> and trying to build up a second front against the manufacturer
> supported work.
It's not true.
> I'm seriously for a new Maintainer election here, let's see what will
> come up during the next few days.
Keep working Markus.
Cheers,
Douglas
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-26 4:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 14:26 [linux-dvb] [ANNOUNCE] DVB API improvements End-user point of viwer Sacha
2008-09-25 15:15 ` VDR User
2008-09-25 16:22 ` Jörg Knitter
2008-09-25 17:44 ` Markus Rechberger
2008-09-25 18:19 ` Halim Sahin
2008-09-25 18:36 ` Markus Rechberger
2008-09-25 18:39 ` VDR User
2008-09-25 20:18 ` [linux-dvb] [ANNOUNCE] DVB API improvements End-user point of view Jörg Knitter
2008-09-25 20:40 ` Michael Krufky
2008-09-25 21:00 ` Markus Rechberger
2008-09-25 23:37 ` hermann pitton
2008-09-25 23:51 ` Janne Grunau
2008-09-26 1:14 ` VDR User
2008-09-26 1:18 ` hermann pitton
2008-09-26 1:28 ` Christophe Thommeret
2008-09-26 1:42 ` VDR User
2008-09-26 2:06 ` hermann pitton
2008-09-26 4:09 ` VDR User
2008-09-26 4:06 ` hermann pitton
2008-09-26 9:31 ` Igor M. Liplianin
2008-09-26 1:27 ` Douglas Schilling Landgraf
2008-09-26 4:50 ` Markus Rechberger
2008-09-26 1:58 ` Douglas Schilling Landgraf [this message]
2008-09-26 5:10 ` hermann pitton
2008-09-26 9:31 ` [linux-dvb] [ANNOUNCE] DVB API improvements End-user point of viwer Mika Laitio
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=20080925215806.0bb585a3@gmail.com \
--to=dougsland@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=mkrufky@linuxtv.org \
--cc=mrechberger@gmail.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