From: Marcel Siegert <mws@linuxtv.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Manu Abraham <abraham.manu@gmail.com>,
v4l-dvb-maintainer@linuxtv.org, linux-dvb@linuxtv.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [linux-dvb] Merge multiproto tree
Date: Mon, 01 Sep 2008 18:22:59 +0200 [thread overview]
Message-ID: <48BC16E3.20500@linuxtv.org> (raw)
In-Reply-To: <20080901120601.044ddc30@mchehab.chehab.org>
hello mauro,
Mauro Carvalho Chehab schrieb:
> Hello, Manu,
>
> On Sat, 30 Aug 2008, Manu Abraham wrote:
>
>> Hello Mauro,
>>
>> Please pull from http://jusst.de/hg/multiproto_api_merge/
>> to merge the following Changesets from the multiproto tree.
>
> The need for supporting newer DTV protocols increases day by day, since when
> the first multiproto proposal started to be discussed, about two years ago.
>
> At the end of the last year, Steven send one email to the ML with a different
> API proposal. Yet, people decided to wait for your work to be done. People then
> pinged you, from time to time, asking about the completion of multiproto. All
> the times, your answer were that multiproto were not ready yet for production.
>
how is the actual state of his proposal?
> I'm aware that your solution seems to be more code-complete than Steven's
> proposal.
>
> But the recent activity on the mailing list regarding his idea (and its,
> so far, positive feedback) and the fact that I was anyway planning to
> have a discussion about the future of the DVB-API at the Linux Plumbers
> Conference 2008 are supporting me in my idea of post-poning such a pull to
> a point in time shortly after this event.
with whom? the linuxtv developers or with an attending audience?
i havent been on the list and that active since the "nearly two years war" begun,
thus i am not the one to ack or nack in this pull request.
what i did in the past was just watching what was happening and what was taking
progress - even if it is slow.
users on the linuxtv list started to ask over and over again, when multiproto is
going to be merged. vdr started to support it in a kind of experiment.
due to the lack of spare time and devices :) i do not actually know how productive
the vdr multiproto implementation is, but we should not start the whole discussions again.
if we do not merge multiproto now, we will never do it, i am afraid.
for the future of this project it is more than neccessary to get some progress.
if there are no serious objections to multiproto, mauro, please pull/merge it
within the next few days. to wait until the end of september is time spending without
any sense.
regards
marcel
> Cheers,
> Mauro
>
> _______________________________________________
> 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-01 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 11:59 Merge multiproto tree Manu Abraham
2008-08-30 12:24 ` Peter Zijlstra
2008-08-30 12:26 ` Willy Tarreau
2008-08-30 12:40 ` Peter Zijlstra
2008-09-01 1:08 ` [v4l-dvb-maintainer] " hermann pitton
2008-09-01 4:08 ` Peter Zijlstra
2008-09-02 0:16 ` hermann pitton
2008-09-01 15:06 ` Mauro Carvalho Chehab
2008-09-01 16:22 ` Marcel Siegert [this message]
2008-09-01 20:33 ` Manu Abraham
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=48BC16E3.20500@linuxtv.org \
--to=mws@linuxtv.org \
--cc=abraham.manu@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@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