Weirdness with svn log after a svn check in

["Shatzer, Larry" <La...@Spirent.com>]

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. If
you do a svn update, then svn log, the entry is now there in the output. One
would think that the log entry would be there when you did the svn log right
after the commit. I can understand why this does not work as expected, since
the directory needed to be updated, but I would imagine that the check in
would update that as well. I hope this makes sense.

It is no big deal, but just a gotcha since I was expecting the log message
to be there.

-- Larry

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Weirdness with svn log after a svn check in

["C. Michael Pilato" <cm...@collab.net>]

"Shatzer, Larry" <La...@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