Hello,
I've configured Trac to submit a message to the ML too
so I think, from now it is better to attach patches to the tickets
Thanks
Vadim
I've configured Trac to submit a message to the ML too
Ludovico Cavedon wrote:
On Sat, Dec 27, 2008 at 9:44 AM, Andreas Schneider <[email protected]> wrote:
On Friday 26 December 2008 16:28:57 Ludovico Cavedon wrote:
I have three new patches attached to an explaining ticket:
- http://trac.qutecom.org/ticket/25
syntax error in CMakeLists-install-linux.txt
I've sent patch for this too. So is the preferred way to send patches the
mailing list or is it the ticket system. I don't read all the ticket, cause
there is no mailing list for the tickets. Yes, trac supports sending mails to
a mailinglist if you create or edit a ticket.
This time I tried with tickets. I do prefer using tickets, because it
is more tidy and clear, but I am afraid nobody is notified about that.
As you said, having a ML for that would be better.
http://www.cynapses.org/tmp/patches/qutecom/
- http://trac.qutecom.org/ticket/26
race condition during re-initialization of libpurple
Can you use the external libpurple library with this patch or is it still
unsafe?
No, I am not using external libpurple yet (because of
http://developer.pidgin.im/ticket/7761).
The code is curently unsafe (and has been unsafe for long time).
However, after applying the patch to avoid memory leak on libpurple
reinitialization (nullptr-noleak.patch), the chance for this race
condition to go wrong has increased because libpurple_core_quit() is
taking longer to complete (freeing some structures)
- http://trac.qutecom.org/ticket/29
compilation fails with libavcodec version 52
I've already send a patch to the mailinglist for this. Remove the line
completely, cause rtp_mode isn't even used in the internal version of ffmpeg.
Sorry, I thought I checked your patches, but I must have missed some
:( They would have saved me some time!
This is one reason I think tickets would be better!
Vadim, what do you think?
Thanks,
Ludovico
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
