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

Re: how to predict copy behavior?!

From: A.T.Hofkamp <a.t.hofkamp_at_tue.nl>
Date: 2005-09-05 18:55:54 CEST

Ben Collins-Sussman wrote:
> On Sep 5, 2005, at 11:22 AM, A.T.Hofkamp wrote:
>> Ben Collins-Sussman wrote:
>>> On Sep 5, 2005, at 8:43 AM, A.T.Hofkamp wrote:
>>>> This kind of things happens often with me, for some reason copying
>>>> and moving files/dirs at the file system is easy (I almost never
>>>> make mistakes there), while with svn I often end up with a result
>>>> I don't intended/wanted.
>>> Both 'svn cp' and 'cp' follow the same basic rule when you run
>>> 'copy A B':
>>> if B exists:
>>> create B/basename(A)
>>> else:
>>> create B, where B == basename(A)
>> I don't understand what you mean by "where B == basename(A)", does
>> that imply that you throw away the name B in the latter case?
> Sure, if I run 'svn cp foo/bar/ baz/bop/', and 'baz' is an empty
> directory, then the 'bop' subdir will be created, and it will be an
> identical copy of 'bar'.

So the thing to remember is that svn cp _always_ creates a directory when
copying directories, while cp sometimes doesnot (since '.' means 'all files'
rather than 'directory').


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 5 18:57:27 2005

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.