Re: svn commit, please don't make me tell you the old path for each move

Daniel Shahaf wrote: Stefan Sperling wrote on Fri, Jan 27, 2017 at 10:18:05 +0100: As far as I recall, the concern here has always been about cases where the user is passing specific arguments, e.g. should 'svn up dir', where 'dir/child' was moved to 'otherdir/child', update just 'dir' or both

Re: svn commit, please don't make me tell you the old path for each move

Stefan Sperling wrote on Fri, Jan 27, 2017 at 10:18:05 +0100: > As far as I recall, the concern here has always been about cases where > the user is passing specific arguments, e.g. should 'svn up dir', where > 'dir/child' was moved to 'otherdir/child', update just 'dir' or both 'dir' > and

Re: segfault with new conflict resolver

On Sat, Jan 28, 2017 at 01:47:03PM +0100, Stefan Sperling wrote: > On Sat, Jan 28, 2017 at 01:31:46PM +0100, Stefan Kueng wrote: > > Hi, > > > > trying out the new conflict resolver. Ran into a segfault on my first try: > > Thank you! I will fix this ASAP. Should be fixed by r1780702.

[OT] Going to FOSDEM

I'm going to FOSDEM next weekend, woo-hoo! https://fosdem.org/2017/ Any other svn hackers going? Hope to see you there if so. The ASF emailed a couple of weeks ago indicating the ASF would have a stand and a few ASF people will be attending, although no-one that I know. There's no

Re: segfault with new conflict resolver

On Sat, Jan 28, 2017 at 01:31:46PM +0100, Stefan Kueng wrote: > Hi, > > trying out the new conflict resolver. Ran into a segfault on my first try: Thank you! I will fix this ASAP. > libsvn_client\conflicts.c, function find_modified_rev(): > > if there is no author for a commit, then we get a

segfault with new conflict resolver

Hi, trying out the new conflict resolver. Ran into a segfault on my first try: libsvn_client\conflicts.c, function find_modified_rev(): if there is no author for a commit, then we get a segfault here: /* No paths were changed in this revision. Nothing to do. */ if (!