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

RE: Issue #3294

From: Bert Huijben <rhuijben_at_sharpsvn.net>
Date: Wed, 25 Mar 2009 10:39:42 +0100

> -----Original Message-----
> From: Edmund Wong [mailto:edmund_at_belfordhk.com]
> Sent: woensdag 25 maart 2009 4:44
> To: dev_at_subversion.tigris.org
> Subject: Issue #3294
> Hi,
> I was reading up issue #3294. I noticed at the end,
> pburba stated:
> "Fixed the 'path not found' bug noted in desc1 in r33693."
> Would this mean that this issue is fixed? and if so, should
> the status be changed to Fixed/Resolved?
> Clarifications appreciated.

I think the log message of r33693 answers that question:
Fix merge bug noted in, but unrelated to, issue #3294. See 'that error at
the end is probably unrelated to the bug this issue is about' in

* subversion/libsvn_client/merge.c
  (filter_self_referential_mergeinfo): Don't try to filter self-referential
  mergeinfo on paths that are scheduled for addition.

* subversion/tests/cmdline/merge_tests.py
  (no_self_referential_filtering_on_added_path): New test that demonstrates
  the bug.
  (test_list): Add no_self_referential_filtering_on_added_path.
I read that as that the "path not found" error occuring in the issue is
resolved, but that this doesn't resolve the real issue described as issue
#3294. (For that it should allow merges from separate urls to the same

But I do remember some other work on this other issue, so it could be that
the issue is resolved by a few other patches.


Received on 2009-03-25 10:39:59 CET

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