Re: rename hides new file until commit

Ben Collins-Sussman wrote:
> On Thu, 2004-01-01 at 18:54, Garret Wilson wrote:
>>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.

Well, let's say I do the following on an empty repository:

*Example 1*
type [cat] "Hello World!" >> foo.txt
svn status

I would probably get something like this:

! foo.txt

which means that there is a file, foo.txt, in the tree that has not yet
been added to the repository.

If I instead have a repository that already contains a foo.txt and I do
the following:

*Example 2*
svn ren foo.txt bar.txt
type [cat] "Hello World!" >> foo.txt
svn status

I would think that the *new* foo.txt in Example 2 has the same
relationship to the repository as does the foo.txt in Example 1---that
is, it is a file in the tree that has not yet been added to the
repository. I would therefore expect the following:

! foo.txt

As "svn status" tells all the scheduled actions, I suppose it would list:

D foo.txt
A bar.txt
! foo.txt

(The way I assume (and hope) subversion works, the file indicated by "D
foo.txt" is a completely separate file than that indicated by "!
foo.txt"---just as distinct as if they were named "alpha.txt" and
"beta.txt".)

Before commiting, I always want to make sure I've added all files to the
repository. With the current "svn status" functionality, I can never
know from the "svn status" output if all files in the directory have
been scheduled for addition to the repository before commit.

Garret

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