[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn log default behaviour

From: Michael Suess <mike_ml_at_suessnetz.de>
Date: 2003-10-22 14:00:03 CEST

Hi Subversion developers,

am I the only one, who thinks that the default behaviour of "svn log" could be
improved? I am presently only using subversion in single-user mode (meaning I
am the only person updating my repositories), and the basic steps at the
beginning of my workday are like this:

$ cd working/copy
$ svn log
*log messages fly by, and stop at revision 1*
"Damn, I did not want to see that, I want to see the last changes!"
*scroll, scroll*
"Grummel, forgot to update again, the last changes are not included!"
$ svn up

And at this point, I usually do, what I should have done all along:
$ svn log -r1:HEAD

So I am basically having two issues that bother me:
1. svn log defaults to reverse recursive behaviour
2. svn log defaults to listing all changes up to BASE, not HEAD

I guess point number two is only an issue for me, because I am the only one
working on my personal repository. If that was not the case, I would have to
update my working copy more often anyways. So I am not going to suggest
changing the default behaviour of svn log to svn log -r1:HEAD.

But whats the reason for the reverse recursive behaviour? I know svn log
-r1:BASE would suit me better...

Michael Suess

"What we do in life, echos in eternity..."
Michael Suess 
Public PGP key: http://www.suessnetz.de/michael/michaelsuess.gpg
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 22 14:00:59 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.