Re: branching and switch question

On 2004-08-26 08:38-0500, kfogel@collab.net wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
> > Here's an example:
> >
> > When you run 'svn rm foo; svn commit':
> >
> > 1. a new repos revision is created where foo is gone, say, rev N.
> > 2. foo is (effectively) removed from your .svn/entries file
> > 3. the working parent-dir of foo is still at rev N-1.
> >
> > Technically, your working parent-dir is "out of sync" with reality: it
> > claims to be at rev N-1, yet it's missing foo. But, when you run 'svn
> > copy working-copy URL', a pristine version of the parent directory is
> > used to build the server-transaction. The file seems to magically
> > reappear in the transaction, and the URL doesn't look like a perfect
> > reflection of your working-copy anymore.
> >
> > I'm not sure if this is a bug or not. :-)
>
> This is a bug, but are you absolutely sure it's true?

I would say it isn't true:

export svn_repo="file://`pwd`/repo"
svn mkdir -m '' $svn_repo/trunk
svn mkdir -m '' $svn_repo/branches
svn co $svn_repo/trunk wc
cd wc/
svn mkdir dir
svn ci -m ''
cd dir
echo 'file 1 ' > file1
echo 'file 3 ' > file2
svn add file*
svn ci -m ''
svn rm file1
svn ci -m ''
svn cp . $svn_repo/branches/b1 -m ''
svn ls $svn_repo/branches/b1
cd ..
svn st -uv

BR, Jani

-- 
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org