Re: rename hides new file until commit

On Thu, 2004-01-01 at 18:54, Garret Wilson wrote:
> I'm not sure if this bug is covered under issue 895 or 898, but here it
> is just in case.
>
> Steps:
> svn ren foo.txt bar.txt

Ok, so now foo.txt is scheduled for deletion, and bar.txt is a new
(copied) file, scheduled for addition-with-history. The working
'foo.txt' is also gone at this point.

> type [cat] "Hello World!" >> foo.txt

This creates a new file called foo.txt

> svn status
>
> (Subversion then lists that bar.txt has been added and that foo.txt has
> been deleted.)

The deletion and addition are *scheduled*, they haven't happened yet.

>
> svn commit

Now the deletion and addition have actually happened.

> svn status
>
> (After a commit, there the *new* foo.txt sits, and it hasn't been added
> to the repository.)

This is correct. What's left over is an unversioned 'foo.txt' that you
created way back in the beginning of the recipe. 'svn status' shows a
question mark next to it, because it's unversioned.

>
> Shouldn't "svn status" have listed that there was a new foo.txt that had
> not been added to the repository? Would "svn add foo.txt" have worked
> before the first commit?

I'm not understanding you.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 2 02:31:22 2004