Question

Something I don’t understand about how SVN displays log output. Suppose I have a project at revision 10. I then alter a subfile in the project, which is now at revision 11. The svn log command now shows me the following:

svn log -vv 
            r10 ...
            ------
            r9 ...
            ------
            r8 ...

However, the lastest change (r11) shows up only if I specify the filename:

svn log -vv ChangedFilename
            r11 ...

Shouldn’t r11 show up in the first command as well?

Answer 1

Explanation is in the handbook:
http://svnbook.red-bean.com/en/1.5/svn.tour.history.html#svn.tour.history.log

Why Does svn log Not Show Me What I Just Committed?

If you make a commit and immediately
type svn log with no arguments, you
may notice that your most recent
commit doesn’t show up in the list of
log messages. This is due to a
combination of the behavior of svn
commit and the default behavior of svn
log. First, when you commit changes to
the repository, svn bumps only the
revision of files (and directories)
that it commits, so usually the parent
directory remains at the older
revision (See the section called
“Updates and commits are separate” for
an explanation of why). svn log then
defaults to fetching the history of
the directory at its current revision,
and thus you don’t see the newly
committed changes. The solution here
is to either update your working copy
or explicitly provide a revision
number to svn log by using the
–revision (-r) option.