[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Patch policy for subversion beginner (was: Re: Segmentation fault when not using -m option.)

From: Robert North <aqh4uyrs3e02_at_sneakemail.com>
Date: 2002-12-09 19:50:58 CET

Garrett Rooney rooneg-at-electricjellyfish.net |Subversion list| wrote:

> Robert North wrote:
>> Just downloaded subversion (0.16) to see how it compared to CVS.
>> No sooner had I started using it, then I got segfaults of the
>> following commands:
>> import, cp, mkdir.
>> I could avoid the segfaults by adding message with the -m option.
>> Is this a known bug?
>> I would expect so, but nothing seems to be up on the Issue tracking
>> part of the web site.
>> Also, might this be fixed by the fix for issue 1027?
> it's quite possible. i never actually reproduced a crash for that
> issue, but i imagine it would look somethign like that. try adding
> the fix (just change 'char *msg2;' to 'char *msg2 = NULL;' in
> subversion/clients/cmdline/util.c) and rebuilding.
> -garrett

Thanks for the suggestion.
Rotering suggested much the same thing, but fixed it by grabbing a new
subversion from the repository.

This brings me to how I should start patching:
I could either grab the latest subversion trunk from the subversion
Or do ad-hoc patches for each issue I trip over.

Which method would people suggest is best to maximise subversion stability?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 9 19:52:05 2002

This is an archived mail posted to the Subversion Dev mailing list.