Re: Weirdness with svn log after a svn check in

"Shatzer, Larry" <Larry.Shatzer@Spirent.com> writes:

> Change a file in your working copy, commit, and then do a svn log
> (with no other parameters) and you get the svn log for the
> directory, but your recent commit is not there listed. Do a svn log
> on the file itself, it shows up

That's because, like every other svn command, an action on a working
copy path defaults to that path's BASE revision. Because you
committed a file, your directory is now one revision out of date, but
your file is up-to-date.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 1 20:06:55 2004