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

Re: svn diff, depth not working

From: Branko Čibej <brane_at_wandisco.com>
Date: Mon, 18 Nov 2013 20:23:17 +0100

On 18.11.2013 20:05, Stefan Kueng wrote:
> Hi,
>
> Running
> $ svn diff folder --depth=empty
> still produces the diff for all added children as well, even though
> the depth was set to empty.
>
>
> $ mkdir folder
> $ echo test > folder/file
> $ svn add folder
> $ svn diff folder --depth=empty > patch.diff
>
> now the file patch.diff also contains the diff for folder/file.
>
> This with the latest build from the 1.8.x branch.

Looks like this is an edge case for newly added directories:

$ svn --version --quiet
1.8.4
$ svnadmin create r
$ svn co file://`pwd`/r w
Checked out revision 0.
$ cd w
$ svn mkdir D
A D
$ touch D/f
$ svn add D/f
A D/f
$ svn diff --depth empty D
Index: D/f
===================================================================
brane_at_zulu:/tmp/test/w$ svn ci -mm
Adding D
Adding D/f
Transmitting file data .
Committed revision 1.
$ svn ps svn:ignore x D
property 'svn:ignore' set on 'D'
$ echo foo >> D/f
$ svn diff --depth empty D
Index: D
===================================================================
--- D (revision 1)
+++ D (working copy)

Property changes on: D
___________________________________________________________________
Added: svn:ignore
## -0,0 +1 ##
+x
$ svn diff D
Index: D/f
===================================================================
--- D/f (revision 1)
+++ D/f (working copy)
@@ -0,0 +1 @@
+foo
Index: D
===================================================================
--- D (revision 1)
+++ D (working copy)

Property changes on: D
___________________________________________________________________
Added: svn:ignore
## -0,0 +1 ##
+x

-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane_at_wandisco.com
Received on 2013-11-18 20:23:52 CET

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

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