Re: SWIG Python - memory growing out of bounds

On 29 Jan 2006 14:00:02 +0100, Lars Gullik Bj=F8nnes <[email protected]> wr=
ote:
> | Thanks for your bug report! This bug has been fixed in Subversion
> | trunk and the fix should be included with 1.3.1. If you would like to
> | fix your local copy, please see the patch included in the Trac issue:
> | http://projects.edgewall.com/trac/ticket/2620
>
> Thanks a lot for that. I had already seen your earlier response on
> this list and also on the trac ticket.
>
> Just to be clear: Is it correct that to test the fix I do not have to
> change anything on the server side (svnserve), it is only on the
> client side the fix has to be applied? (I cannot really make changes
> to the server installation at this time)

This fix is client side only. (The server does not need to be
updated.) Let me know whether it helps!

> | Sorry for the delayed response! In future, please send bug reports to
> | <[email protected]>. If the bug is regarding the Python
> | bindings you can cc me to bring it to my attention.
>
> I'll do that.
>
> Perhaps the language on
> http://subversion.tigris.org/project_issues.html "Issue tracker guideline=
s" should be
> relaxed a bit?
>
> After beeing chastised a bit ealier, I was reluctant on approaching
> the dev list directly.

A safe rule is: If you are trying to help Subversion development, send
your mail to dev@. For this reason, bug reports are always welcome on
the dev@ list, especially if the bug report contains all the
information we need to reproduce the bug on our own systems.

We should probably update project_issues.html and bugs.html to note
that detailed bug reports are welcome on the dev@ list. I am often
disappointed to miss important bug reports because they were only sent
to the users@ list, which I do not read as often.

Cheers,

David

--
David James -- http://www.cs.toronto.edu/~james