You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Michael Suess <mi...@suessnetz.de> on 2003/10/22 12:00:03 UTC
svn log default behaviour
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
Re: svn log default behaviour
Posted by Michael Suess <mi...@suessnetz.de>.
On Wednesday 22 October 2003 18:18, Ben Collins-Sussman wrote:
> Michael Suess <mi...@suessnetz.de> writes:
> > Thanks, while trying it out, i noticed, that
> > $ svn log -r{yesterday}:HEAD
> > shows one revision too much (in my case, one from 10-14-2003, which is
> > not exactly what I call yesterday ;-) ). Is this intentional as well?
>
> Look at the grey box at the bottom of this page:
>
> http://svnbook.red-bean.com/html-chunk/ch03s03.html#svn-ch-3-sect-3.2
Now look at that, shame on me for not looking there first :-)
/me retreats back into the back of the room, where all the lurkers are,
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
Re: svn log default behaviour
Posted by Ben Collins-Sussman <su...@collab.net>.
Michael Suess <mi...@suessnetz.de> writes:
> Thanks, while trying it out, i noticed, that
> $ svn log -r{yesterday}:HEAD
> shows one revision too much (in my case, one from 10-14-2003, which is not
> exactly what I call yesterday ;-) ). Is this intentional as well?
Look at the grey box at the bottom of this page:
http://svnbook.red-bean.com/html-chunk/ch03s03.html#svn-ch-3-sect-3.2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn log default behaviour
Posted by Michael Suess <mi...@suessnetz.de>.
On Wednesday 22 October 2003 17:50, Ben Collins-Sussman wrote:
> Michael Suess <mi...@suessnetz.de> writes:
> > On Wednesday 22 October 2003 16:53, kfogel@collab.net wrote:
> > > Log messages are going to fly by on your console either way, unless
> > > you redirect to a file or pipe through a paging program such as
> > > 'more'.
> >
> > Ah, I finally see the light :-). You are right, if you want to save the
> > output in a file, it is more useful this way around. Had not thought of
> > that, cause my repositories are on the same computer anyways...
> >
> > Thanks for taking the time to answer, proposal withdrawn :-)...
>
> By the way, if I want to see "the last few" log messages, I often run
>
> $ svn log -r{yesterday}:HEAD
>
> ...it usually works out pretty well. :-)
Thanks, while trying it out, i noticed, that
$ svn log -r{yesterday}:HEAD
shows one revision too much (in my case, one from 10-14-2003, which is not
exactly what I call yesterday ;-) ). Is this intentional as well?
Asks,
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
Re: svn log default behaviour
Posted by Ben Collins-Sussman <su...@collab.net>.
Michael Suess <mi...@suessnetz.de> writes:
> On Wednesday 22 October 2003 16:53, kfogel@collab.net wrote:
>
> > Log messages are going to fly by on your console either way, unless
> > you redirect to a file or pipe through a paging program such as
> > 'more'.
>
> Ah, I finally see the light :-). You are right, if you want to save the output
> in a file, it is more useful this way around. Had not thought of that, cause
> my repositories are on the same computer anyways...
>
> Thanks for taking the time to answer, proposal withdrawn :-)...
By the way, if I want to see "the last few" log messages, I often run
$ svn log -r{yesterday}:HEAD
...it usually works out pretty well. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn log default behaviour
Posted by Michael Suess <mi...@suessnetz.de>.
On Wednesday 22 October 2003 16:53, kfogel@collab.net wrote:
> Log messages are going to fly by on your console either way, unless
> you redirect to a file or pipe through a paging program such as
> 'more'.
Ah, I finally see the light :-). You are right, if you want to save the output
in a file, it is more useful this way around. Had not thought of that, cause
my repositories are on the same computer anyways...
Thanks for taking the time to answer, proposal withdrawn :-)...
Michael
--
"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
Re: svn log default behaviour
Posted by kf...@collab.net.
Michael Suess <mi...@suessnetz.de> writes:
> But whats the reason for the reverse recursive behaviour? I know svn log
> -r1:BASE would suit me better...
So the "recursive" is not the issue, just the "reverse"?
We chose the same default that both CVS and ChangeLog format use. The
point is that the output can put in a file, and when you read the
file, the most recent activity is at the top, not the bottom.
Personally, I love it. Your Mileage May Vary :-).
Log messages are going to fly by on your console either way, unless
you redirect to a file or pipe through a paging program such as
'more'.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org