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

"Dale Worley" <dworley@pingtel.com> writes:

> Getting away from how Subversion should handle the situation,

Yes, you're right..

> the key to not getting confused is to remember that directories have
> BASEs as well as files, and that "svn log" implicitly searches the span
> from rev 1 to the BASE of ".". "svn info" will report the current BASE
> of any directory, and "svn update" will move the BASE of a directory to
> the current HEAD.

After discussing this with you guys, I can see that the newbie confusion
that I (and a collegue of mine) suffered was caused by:

 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 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.

 3. The default revision range for svn log is "-rBASE:1", where I had
    assumed it to be "-rHEAD:1". This is an "RTFM more closely" item for
    me.

I would be interested in knowing _why_ the commit semantics of directories
and files need to differ. I'm sure there are good reasons. Can anyone here
explain the ideas behind this, or point me to a document or mailing list
thread that covers this?

Thanks for helping me understand these subtleties! :-)

Best regards,
Niels

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 16 23:02:14 2004