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

Re: svn up -p

From: Vladimir Prus <ghost_at_cs.msu.su>
Date: 2002-11-06 11:45:46 CET

Andreas J. Koenig wrote:

> >> Has anybody considered a "print" command instead? Re-using "update"
> >> for a purpose that has nothing to do with updating seems odd to me.
>
> > Or "get" command... I thought about it. However, a flag to update is
> > CVS usage which is not that confusing, IMO. On the other hand adding
> > a new command for relatively rare operation is not desirable. When occasionally
> > trying to use some other SCM tool, I was very confused by a couple of
> > screens of commands.
>
> -- "get" also has a connotation of copying, "print" is usually stdout
> and with shell redirection can be turned into a "get".

No opinion here.

>
> -- I don't believe it is a rare operation. Not only tkdiff will need
> to download complete files, everybody working with a powerful
> "diff" application needs it all the time:
>
> svn print -r 12 foo > foo@12
> svn print -r 14 foo > foo@14
> # now fire your favorite diff application

I belive support for custom diff programs is expected some day? So this
use is not that important.

> -- Powerful software has to live with the fact that it has always too
> many great features. Good naming helps navigate. Hiding powerful
> commands just makes the FAQ longer:-)

As I've said, I don't think this operation is frequent enough to
warrant a command. You have different option. What others think?

- Volodya

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 6 11:44:52 2002

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.