Menu
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?
880
Shows log messages from the repository. If no arguments are supplied, svn log shows the log messages for all files and directories inside (and including) the current working directory of your working copy. You can refine the results by specifying a path, one or more revisions, or any combination of the two.
To find information about the history of a file or directory, use the svn log command. svn log will provide you with a record of who made changes to a file or directory, at what revision it changed, the time and date of that revision, and, if it was provided, the log message that accompanied the commit.
echo Enter the URL of the repository from which to extract the logs. REM Execute SVN command to get all the commit logs from the defined repository. "svn.exe" must be in the path! REM Launch the generated file in Excel in "embedded" mode, with Current Directory as the start folder.
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.
174
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
