Strange. I had no idea that cp did that.
Is there another switch I should be specifying to override this behavior
(say to make it prompt or to throw an error or something?)? Or is there
a way we can easily tell if a directory already exists?
I think we can mostly get around the problem, but the behavior does seem
somewhat counterintuitive.
William Gant
Programmer Analyst I
Brookdale Senior Living
111 Westwood Place Suite 200
Brentwood, TN 37027
(615) 564-8138 P
(615) 234-7309 F
wgant_at_brookdaleliving.com
-----Original Message-----
From: Stefan Sperling [mailto:stsp_at_elego.de]
Sent: Monday, July 13, 2009 11:18
To: Will Gant
Cc: users_at_subversion.tigris.org
Subject: Re: Is this a bug or a feature?
On Mon, Jul 13, 2009 at 11:10:52AM -0500, Will Gant wrote:
> I guess I'm still a bit lost. I'm puzzled as to why subversion copies
> the new data into a child directory of the target rather than throwing
> an error out or overwriting. I'm not sure what the purpose of that
> feature would be.
It's consistent with the way UNIX cp works.
Stefan
-----------------------------------------
This email may contain confidential protected health information
and/or attorney privileged information. If received in error, see
our Privacy Statement at
http://www.brookdaleliving.com/privacy-policy.aspx
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2370985
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-13 18:37:25 CEST