Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

"svn log" not showing all recent commits

Tags:

svn

Note: This is probably a no-brainer for experienced SVN users, but it stumped me for quite awhile...so here's hoping this will help someone like me!

After issuing svn log from the command line, I noticed that several recent commit messages were missing. I knew that these messages were correctly saved in my repository because they were showing up in my SVN client (RapidSVN). I just couldn't figure out why they wouldn't be visible using the command line version of svn.

Answer below...

like image 947
robguinness Avatar asked May 28 '13 08:05

robguinness


People also ask

How do I see recent commits in svn?

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.

How do I view svn logs?

Examples. You can see the log messages for all the paths that changed in your working copy by running svn log from the top: $ svn log ------------------------------------------------------------------------ r20 | harry | 2003-01-17 22:56:19 -0600 (Fri, 17 Jan 2003) | 1 line Tweak.

Does svn allow editing commit message in history?

By default, the log message property (svn:log) cannot be edited once it is committed. That is because changes to revision properties (of which svn:log is one) cause the property's previous value to be permanently discarded, and Subversion tries to prevent you from doing this accidentally.

What is commit in svn?

svn commit will send any lock tokens that it finds and will release locks on all PATH s committed (recursively) unless --no-unlock is passed. Tip. If you begin a commit and Subversion launches your editor to compose the commit message, you can still abort without committing your changes.


1 Answers

The problem had to do with my poor understanding of what svn log was showing. With no other arguments supplied, it outputs log messages from the working copy of the log, not from the actual repository. Thus, issuing svn update will bring the working copy up-to-date with the repository, and then svn log will reflect all recent commits. Duh! ;-)

like image 78
robguinness Avatar answered Sep 21 '22 08:09

robguinness