[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: Andreas J. Koenig <andreas.koenig_at_anima.de>
Date: 2002-11-06 09:57:08 CET

>>>>> On Wed, 06 Nov 2002 11:36:42 +0300, Vladimir Prus <ghost@cs.msu.su> said:

> Andreas J. Koenig wrote:
>>>>>>> On Tue, 05 Nov 2002 19:54:56 -0600, "B. W. Fitzpatrick" <fitz@red-bean.com> said:
>>>>>>
>> >> > I believe the "-p" in CVS stood for "pipe", as in "pipe to
>> stdout".
>> >> > Something involving "pipe" might be better; if you use
>> >> > "--print-only", people are going to think it has something to do
>> >> > with their printer.
>> >> >> I think the important word here is 'stdout', not pipe.
>> People need to
>> >> realize that the file comes out of the standard output.
>> >> >> But that's just me :-)
>> > I agree. is --stdout too weird/unix centric?
>> 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".

-- 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

-- 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:-)

-- 
andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 6 09:57:58 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.