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

svn diff --notice-ancestry: strange behavior

From: Nick Patavalis <npat_at_efault.net>
Date: 2004-08-03 00:36:51 CEST

I noticed the following strange behavior using svn 1.0.6 (built from
the source tarball, running on linux, with db-4.2.52, with apr from
apache 2.0.50, accessing the repos through svnserve). I do:

   svn diff --notice-ancestry \
            --old svn://host/rep/proj/branches/b1/dir1 \
            --new svn://host/rep/proj/trunk/dir1

And I see a file in "dir1" getting deleted and added-back again with
exactly the same contents. This what I expected to see. Then I do:

   svn diff --notice-ancestry \
            --old svn://host/rep/branches/b1/dir1 \
            --new ./dir1

Where "dir1" is a fully up-to-date working copy, and I see no
differences. It seems as if "--notice-ancestry" was ignored in the
latter invocation. Is this reasonable, or am I doing something wrong?

Thanks in advance for for your replies

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 3 00:37:10 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.