From: Manu Abraham <abraham.manu@gmail.com>
To: Andy Walls <awalls@radix.net>
Cc: Steven Toth <stoth@linuxtv.org>,
linux-dvb@linuxtv.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-dvb] Multiproto API/Driver Update
Date: Mon, 15 Sep 2008 01:01:54 +0400 [thread overview]
Message-ID: <48CD7BC2.1080708@gmail.com> (raw)
In-Reply-To: <1221425146.4278.30.camel@morgan.walls.org>
Andy,
Andy Walls wrote:
> Manu,
>
> Though I can't read much German, after looking at the jusst.de website I
> can't help but think that you as well have financial interests driving
> your actions. If so, then your statements display quite a bit of
> hypocrisy.
To your utter disappointment as i should say, i am not working for any
vendor, but just get device support out to the community.
The jusst.de domain is owned by Julian Scheel who runs Jusst
Technologies, just happened to offer me hosting for me repositories for
my work, using full ssh access, so that my workflow is easier.
Not that i have anything to do with jusst.de otherwise. OTOH, i do have
the patches at kernel.org
Maybe Julian can comment on this to make things more clearer on the
financial interests.
> Manipulating (i.e. stalling) the timing of Multiproto being merged into
> the v4l-dvb tree or kernel, for you or your employer's gain, would be
> little different from the motivations you allege Steve of having.
I am not manipulating any timing of multiproto being merged. In fact i
had been away, for a few months due to certain reasons, that you are
perfectly aware by now as far as i can understand. So the points that
you raise are quite baseless.
> Since the major gripe I'm reading on the list "is that multiproto has
> taken too long" and since it seems to me the only thing that shook it
> loose was a competing proposal, please save the venom for when you
> actually have some clear moral high-ground to stand on. I don't see it
> from here.
Crap, just read above.
> As for the technical superiority of either API proposal; that probably
> just doesn't matter. I've seen policy/political decisions force
> suboptimal technical solutions at work time and time again. If you
> really believe you have a superior product technically; then perhaps you
> should work to make it superior politically as well. Mud-slinging can't
> be a good long term strategy toward that end.
I don't have to do any mud-slinging, just wrote the exact facts out here.
Regards,
Manu
next prev parent reply other threads:[~2008-09-14 21:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <466109.26020.qm@web46101.mail.sp1.yahoo.com>
[not found] ` <48C66829.1010902@grumpydevil.homelinux.org>
[not found] ` <d9def9db0809090833v16d433a1u5ac95ca1b0478c10@mail.gmail.com>
[not found] ` <48CC42D8.8080806@gmail.com>
2008-09-13 22:56 ` [linux-dvb] Multiproto API/Driver Update Markus Rechberger
2008-09-13 23:31 ` Manu Abraham
2008-09-14 2:10 ` Markus Rechberger
2008-09-14 14:27 ` Steven Toth
2008-09-14 15:38 ` Markus Rechberger
2008-09-14 17:02 ` Steven Toth
2008-09-14 18:51 ` Manu Abraham
2008-09-14 20:45 ` Andy Walls
2008-09-14 21:01 ` Manu Abraham [this message]
2008-09-14 22:20 ` Andy Walls
2008-09-14 22:36 ` Manu Abraham
2008-09-15 4:23 ` hermann pitton
2008-09-14 21:03 ` Manu Abraham
2008-09-15 5:50 ` Julian Scheel
2008-09-15 15:42 ` Michael Krufky
2008-09-19 10:58 ` Julian Scheel
2008-09-19 19:55 ` VDR User
2008-09-24 16:54 ` Oliver Endriss
2008-09-15 23:10 ` Andy Walls
2008-09-16 2:55 ` hermann pitton
2008-09-14 3:39 ` hermann pitton
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=48CD7BC2.1080708@gmail.com \
--to=abraham.manu@gmail.com \
--cc=awalls@radix.net \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stoth@linuxtv.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