hi,

my apologies for not having responded to you patch, but i did not get a
nofitication mail from sf about this so i was unaware of your contribution.
in general, it would probably help if you post the patch (or the link to the
sf patch entry) directly on this list instead.

i'll have a look at the patch tomorrow, if it looks good i'll apply and make
a new pycurl release.

thanks,
    - kjetil

On 1/30/06, Paul Pacheco <paulpach_at_gmail.com> wrote:
>
> Hi,
>
> I found and fixed a memory leak in pycurl and posted the patch in
> sourceforge
> here:
>
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1326773&group_id=28236&atid=392777
>
> The original fix was for 7.14.0, but the bug is still there in 7.15.0 (and
> the
> patch does apply cleanly) It has been over 3 months since I posted the
> patch,
> and to this date it has not been applied or commented upon.
>
> So my question is: is there a better way to submit patches? what can I do
> to
> expedite patch merging?
> _______________________________________________
> http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-python
>

_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-python
Received on 2006-01-30