Oliver Endriss wrote:
Marcel Siegert wrote:
can everybody _please_ stop this unnessessary discussion?
Full ack! I'm really tired reading these garbage threads.
@all,
I suggest the following:
1a Review the API extensions (dvb_frontend.h).
1b Commit them.
2a Review dvb_core
Oliver Endriss wrote:
Manu Abraham wrote:
Oliver Endriss wrote:
@all,
I suggest the following:
1a Review the API extensions (dvb_frontend.h).
1b Commit them.
2a Review dvb_core modifications.
2b Commit them.
3 Commit drivers when they are ready for inclusion.
Will appreciate if you
Marcel Siegert wrote:
can everybody _please_ stop this unnessessary discussion?
Full ack! I'm really tired reading these garbage threads.
@all,
I suggest the following:
1a Review the API extensions (dvb_frontend.h).
1b Commit them.
2a Review dvb_core modifications.
2b Commit them.
3 Commit
Johannes Stezenbach wrote:
On Fri, Oct 12, 2007, Manu Abraham wrote:
Johannes Stezenbach wrote:
Does that mean that Manu has no intentions to get
his multiproto API changes merged?
It will be merged
When? Why hasn't it been merged months ago when HVR4000 worked?
HVR4000 was struggling
Hi,
On Fri, Oct 12, 2007, Marcel Siegert wrote:
can everybody _please_ stop this unnessessary discussion?
When a developer deletes his mercurial repositories and
announces he's going to rewrite the code to be independent
of multiproto, then IMHO it is _necessary_ to find out
why, and how to
Marcel Siegert wrote:
hi,
can everybody _please_ stop this unnessessary discussion?
manu, nobody is playing politics in the moment,
not johannes, not steven, not anyone else.
What was discussed yesterday was that, if you don't do what i write,
i'll just take your code nevertheless as
hi,
can everybody _please_ stop this unnessessary discussion?
manu, nobody is playing politics in the moment,
not johannes, not steven, not anyone else.
maybe sometimes it is hard to understand what people want to
say if you have all the bad past in mind.
what was said in coherence to your
hermann pitton wrote:
Am Mittwoch, den 10.10.2007, 23:44 +0400 schrieb Manu Abraham:
Steven Toth wrote:
If there is a defined workflow, this moaning will stop. With the
moaning on there will be problems and blindly writing mails based on
that, just adds in to the problems at large.
Steven Toth wrote:
Speaking purely for myself, my involvement with linuxtv varies depending
on my other work commitments. For this reason, I do not expect to review
every patch which gets created against the various drivers I've ever
brought to life. So, Manu's idea doesn't work for me, and I
(Corrected a typo)
Steven Toth wrote:
Speaking purely for myself, my involvement with linuxtv varies depending
on my other work commitments. For this reason, I do not expect to review
every patch which gets created against the various drivers I've ever
brought to life. So, Manu's idea doesn't
Steven Toth wrote:
hermann pitton wrote:
Am Mittwoch, den 10.10.2007, 23:44 +0400 schrieb Manu Abraham:
Steven Toth wrote:
If there is a defined workflow, this moaning will stop. With the
moaning on there will be problems and blindly writing mails based on
that,
Steven Toth wrote:
Hi,
After a disappointing multiproto debate on IRC today I've decided to
remove the ~stoth/multiproto and ~stoth/HVR4000 trees from linuxtv.org.
I no longer support the multiproto patches and I'm seeking alternative
ways to deliver the HVR4000 S2 driver to the community.
Johannes Stezenbach wrote:
On Thu, Oct 11, 2007, Steven Toth wrote:
After a disappointing multiproto debate on IRC today I've decided to
remove the ~stoth/multiproto and ~stoth/HVR4000 trees from linuxtv.org.
I no longer support the multiproto patches and I'm seeking alternative
ways to
Georg Acher wrote:
On Thu, Oct 11, 2007 at 05:11:24PM -0400, Steven Toth wrote:
Anyway, sadly, I had to drop support for the HVR4000 via your patches
and I'll have to find a way to reimplement support via another mechanism.
Almost a year ago I've used a very early stage of your
On Fri, Oct 12, 2007, Manu Abraham wrote:
Johannes Stezenbach wrote:
Does that mean that Manu has no intentions to get
his multiproto API changes merged?
It will be merged
When? Why hasn't it been merged months ago when HVR4000 worked?
(If so, then wtf was the point of doing them
Manu Abraham wrote:
Steven,
Steven Toth wrote:
Johannes / Manu,
I'm actually pretty sad about the whole situation. The HVR4000 has been
done for over a year, probably much more. Support for this product in
the main v4l-dvb repository is stuck behind the multiproto tree, and
that's
Markus Rechberger wrote:
Manu Abraham wrote:
Steven,
Steven Toth wrote:
Johannes / Manu,
I'm actually pretty sad about the whole situation. The HVR4000 has been
done for over a year, probably much more. Support for this product in
the main v4l-dvb repository is stuck behind
Steven Toth wrote:
If there is a defined workflow, this moaning will stop. With the
moaning on there will be problems and blindly writing mails based on
that, just adds in to the problems at large.
Thanks for the feedback.
I had some difficulties understanding parts of your email,
Am Mittwoch, den 10.10.2007, 23:44 +0400 schrieb Manu Abraham:
Steven Toth wrote:
If there is a defined workflow, this moaning will stop. With the
moaning on there will be problems and blindly writing mails based on
that, just adds in to the problems at large.
Thanks for the
On Sun, Oct 07, 2007, Artem Makhutov wrote:
I am wondering about the future of the Multiproto API.
me too -- thanks for asking
Will the Multiproto API be part of the upcoming DVB-API, is it just a
short time solution to make the DVB-S2 devices work or is Multiproto the
new DVB-API?
For a
Johannes Stezenbach wrote:
On Sun, Oct 07, 2007, Artem Makhutov wrote:
I am wondering about the future of the Multiproto API.
me too -- thanks for asking
Will the Multiproto API be part of the upcoming DVB-API, is it just a
short time solution to make the DVB-S2 devices work
Steven,
Steven Toth wrote:
Johannes / Manu,
I'm actually pretty sad about the whole situation. The HVR4000 has been
done for over a year, probably much more. Support for this product in
the main v4l-dvb repository is stuck behind the multiproto tree, and
that's going nowhere. People have
Hi,
I am wondering about the future of the Multiproto API.
Will the Multiproto API be part of the upcoming DVB-API, is it just a
short time solution to make the DVB-S2 devices work or is Multiproto the
new DVB-API?
What about Multiproto support by other application?
Is/will VDR, MythTV or any
23 matches
Mail list logo
