Enough people have unthinkingly ackd Davide's message. It deserves some
serious criticism.
> I'm neither Klaus not a regular of this list,
If you say so.
> but I think you're not
> being fair here: Klaus has every right to say he won't develop on a
> community tree; it is, after all, his own fr
> On 09/06/08 16:34, Hans Werner wrote:
> > ...
> > After 145 or so days without any release, there is a lot of code which
> > has been posted as patches implementing vital features (such as H.264)
> > which could immediately be merged in.
>
> If I'm not mist
Original-Nachricht
> Datum: Sat, 06 Sep 2008 18:01:48 +0200
> Von: Udo Richter <[EMAIL PROTECTED]>
> An: VDR Mailing List
> Betreff: Re: [vdr] VDR Development
> Hans Werner wrote:
> > Sourcecaps I believe has existed as a patch for about four *year
Original-Nachricht
> Datum: Sun, 07 Sep 2008 13:31:22 +0200
> Von: Helmut Auer <[EMAIL PROTECTED]>
> An: VDR Mailing List
> Betreff: Re: [vdr] VDR Development (Number of users)
> Hi
> > On 09/05/08 18:38, VDR User wrote:
> >
> >> ... Seeing how
> >> many people have already
Hi,
On Sun, 06 Aug 2006 10:58:17 +0200
Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> daliman wrote:
> > Hi, the number of the patant is shown in the installer. Please
> > tell your question to the patentamt.
> > Greet, DaLiMan
>
> Any chance you might tell us that patent number without the
> ne
Hi,
On Mon, 4 Sep 2006 17:09:12 +0200
"martin" <[EMAIL PROTECTED]> wrote:
> I've problems when implementing the latest 1.4.2.-1 Patch. Here's the
> problem: I used VDR-Admin to change a timer setting. Every time I try to
> save the changed timer, VDR crashes, please see attached strace.
There ha
Hi,
On Fri, 8 Sep 2006 16:02:57 +0200 Clemens Kirchgatterer
<[EMAIL PROTECTED]> wrote:
> > Changing the "free(aux);" to "if(aux) free(aux);" would probably
> > care for that (resembling the earlier behaviour).
>
> code like: if (bla) free(bla); will actually _never_ fix any bug.
> either bla is
Hi,
On Fri, 08 Sep 2006 16:58:10 +0200
Udo Richter <[EMAIL PROTECTED]> wrote:
> I don't agree. The double free assertion wont be issued if you free NULL
> twice.
Of course. Thanks for pointing out my failure & clarification. I should
have thought twice... (and I just read the code for malloc/fr
