cmpilato@collab.net writes:
More thoughts:
> Gareth McCaughan <Gareth.McCaughan@pobox.com> writes:
>
> > Consider the following shell script:
> >
> > #!/usr/local/bin/bash -v
> > BASE=<some directory or other>
> > R=$BASE/svn-r
> > W=$BASE/svn-w
> > rm -rf $R $W
> > svnadmin create $R
> > mkdir $W
> > cd $W
> > mkdir project
> > svn import -m 'initial import' file://$R project project
> > svn co file://$R/project project
> > cd project
> > mkdir a
> > svn add a
> > touch a/b
> > svn add a/b
> > svn commit -m 'add stuff'
> > echo zog >> a/b
> > svn commit -m 'extend a/b'
Note that if right here you add 'svn up', the bug disappears. Why?
Because that will cause both 'a' and 'a/b' to have the same revision.
That, in turn, causes the commit driver to issue only a single add of
'c' as a copy of 'a', which will, as before, include 'a/b'.
> > svn cp a c
> > svn commit -m 'duplicate directory'
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 5 19:25:57 2002