cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)

[Jakub Piotr Cłapa]

Jan Rekorajski wrote:
> On Sat, 10 Sep 2005, Arkadiusz Miskiewicz wrote:
> 
>>On Saturday 10 of September 2005 12:48, Jan Rekorajski wrote:
>>
>>>On Fri, 09 Sep 2005, Arkadiusz Miskiewicz wrote:
>>>
>>>>svn: see how creating diff between release and branch of kdebase package
>>>>is: svn diff svn://anonsvn.kde.org/home/kde/tags/KDE/3.4.2/kdebase \
>>>>svn://anonsvn.kde.org/home/kde/branches/KDE/3.4/kdebase \
>>>>
>>>>>kdebase-branch.diff
>>>>
>>>>_without_ having anything beside svn client locally
>>>
>>>Side note about command line - it's what pisses me the most in svn, the
>>>requirement to type whole long URLs. I don't need to know them, it's the
>>>scm job to remember root dir for a repository/module.
>>
>>svn remembers the urls in the same way as cvs.
>>
>>mkdir /tmp/whatever; cd /tmp/whatever; cvs up -r TAG file
>>won't work. you still need to specify whole 
>>-d:pserver:something at blahblah.pl:/somethingelse 
> 
> I think you didn't get my point. With cvs I do cvs up once and then
> I have ':pserver:something at blahblah.pl:/somethingelse' in CVS/Root
> and I don't have to specify it anymore. With svn every time I want some
> tag/branch I must specify the whole URL for that tag or branch.
> Any svn command that has something to do with tag/branch requires URLs.
> No such requirement with cvs.
> 
> What's interesting is that svn keeps this info in .svn/ and does not use
> it. Sick.

If you checkout tags/ and branches/ (probably empty) than you won't need 
to type the URLs. The URLs are only needed when you want to do 
server-side cp or mv (which is not possible with CVS at all).

-- 
Regards,
Jakub Piotr Cłapa