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

Re: svn log questions

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-12-10 16:01:13 CET

On Dec 10, 2004, at 2:46 AM, Bradley Schick wrote:
> I still wonder why making -rPREV be the previous change revision
> wouldn't
> be a better solution.

There's a design tension between these goals:

   - "optimize every command to behave differently, so that each command
can guess what the user really means", and

   - "define a bunch of concepts, and make them behave consistently
across all commands"

You can't have it both ways, and the svn developers chose to go for the
latter goal.

Another example of this is:

    svn commit foo.c
    svn log

You'd think that 'svn log' would show you the commit to foo.c that you
just made, right? After all, that's what CVS does. But it doesn't...
not without running 'svn up' first. It's been the subject of much
debate, but it's another example of 'consistency' winning out over 'do
what I mean'.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 10 16:04:34 2004

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

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