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

Re: "svn commit" followed by "svn log" doesn't show new revision

From: Niels Skou Olsen <nso_at_manbw.dk>
Date: 2004-11-18 07:23:56 CET

Niels Skou Olsen <nso@manbw.dk> writes:

> Niels Skou Olsen <nso@manbw.dk> writes:
>
>>> Aside note to Ben: in "How Working Copies Track the Repository" the text
>>> refers to files only, such as "each file in a working directory" and
>>> "working file", when there are entries for directories too, and they are
>>> tracked in the same way.
>>
>> I agree that this section should cover directories as well. Especially the
>> state "Locally changed, and out-of-date" has some interesting subtleties
>> with respect to the behaviour of commit/update:
>
> It was a bit late when I wrote this section. Actually the two items below
> apply to *all* four states of the working copy ("Unchanged, and current",
> "Locally changed, and current", "Unchanged, and out-of-date", "Locally
> changed, and out-of-date"):

Dohhh -- of course it only applies when a working copy is in one of the
"Locally changed" states.

>
>> 1. Committing directory changes is handled differently from files, when
>> the working copy is out of date. For directories the commit succeeds,
>> and for files it fails with the "Out of date" error message.
>>
>> 2. When committing a directory change, the directory's BASE revision is
>> not updated, and "svn log" will thus not show the new revision. When
>> committing a file change, the file's BASE revision *is* updated, and
>> "svn log" *will* show the new revision.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 18 07:24:54 2004

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