On Fri, Aug 11, 2006 at 10:13:22PM +0200, Klaus Schmidinger wrote:
> Udo Richter wrote:
> >VDR User wrote:
> >>Klaus, any particular reason you're not releasing the TODO list?
> >
> >Probably to keep expectations down. If feature X is on the todo list,
> >then it might be implemented next week. Or
Ok, I see your points. I personally wouldn't pester him but you're probably right, most of the VDR community would. He (and others) have been developing VDR for a while so they probably know what to expect. ;)
On 8/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> VDR User wrote:> > You coul
> VDR User wrote:
> > You could always just include a disclaimer in the list and refer people
> to
> > it any time they ask questions like those. :)
>
> It would not help, the list would still be full of whinings and moanings
> that, "why *my* important stuff has not been done" (replace *my* with
VDR User wrote:
You could always just include a disclaimer in the list and refer people to
it any time they ask questions like those. :)
It would not help, the list would still be full of whinings and moanings
that, "why *my* important stuff has not been done" (replace *my* with
your name)
Secu
You could always just include a disclaimer in the list and refer people to it any time they ask questions like those. :)On 8/11/06, Klaus Schmidinger <
[EMAIL PROTECTED]> wrote:
Udo Richter wrote:> VDR User wrote:>> Klaus, any particular reason you're not releasing the TODO list?>> Probably to keep
Udo Richter wrote:
VDR User wrote:
Klaus, any particular reason you're not releasing the TODO list?
Probably to keep expectations down. If feature X is on the todo list,
then it might be implemented next week. Or next month. Or next year. Or
in 5 years. Or never.
But people will for sure ask
VDR User wrote:
Klaus, any particular reason you're not releasing the TODO list?
Probably to keep expectations down. If feature X is on the todo list,
then it might be implemented next week. Or next month. Or next year. Or
in 5 years. Or never.
But people will for sure ask every week 'when wi
We haven't even gotten to 1.5 yet so I wouldn't expect a release date for 1.6!Klaus, any particular reason you're not releasing the TODO list?
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
For now or for a long time? like when vdr-1.6 is release?
Klaus Schmidinger wrote:
[EMAIL PROTECTED] wrote:
Hi Klaus
I read yesterday a part of your answer mail to a question of vdr
user:
> In VDR version 1.4 the CA_PMT records (that's the data a CAM needs in
> order to know which PIDs
[EMAIL PROTECTED] wrote:
Hi Klaus
I read yesterday a part of your answer mail to a question of vdr user:
> In VDR version 1.4 the CA_PMT records (that's the data a CAM needs in
> order to know which PIDs it shall decrypt) are sent to all CAMs in
> one CI device. I know that this can be a
Hi Klaus
I read yesterday a part of your answer mail to a question of vdr user:
> In VDR version 1.4 the CA_PMT records (that's the data a CAM needs in
> order to know which PIDs it shall decrypt) are sent to all CAMs in
> one CI device. I know that this can be a problem, and that's why I'm
>
11 matches
Mail list logo
