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

Re: New subversion bug?

From: Bert Huijben <bert_at_qqmail.nl>
Date: Tue, 17 Jun 2014 07:57:55 +0000

At the api level there are soms existent options that we don't map in svn. I'm not sure if these map to the desired --no-target-directory behavior that GNU added though.


Bert






Sent from Windows Mail





From: Branko Čibej
Sent: ‎Tuesday‎, ‎June‎ ‎17‎, ‎2014 ‎9‎:‎29‎ ‎AM
To: users_at_subversion.apache.org





On 16.06.2014 23:54, Ben Reser wrote:


On 6/16/14 8:26 PM, Croft, Joe wrote:


Thank you, but it would be nice to have a command line option to turn off this
feature.

Seems like a reasonable suggestion. I'd suggest --no-target-directory which
mirrors the GNU cp option that provides this functionality. Don't think the
various Windows commands have an equivalent.


Before talking about command-line options (which imply API changes, by the way), can we get some idea about how "svn cp --no-target-directory A B" should be have when B already exists? If we start deleting the target, which we've never done before, that's likely to make lots of people angry when they mess up their repositories (because we don't have a way to properly undo the mess).

-- Brane



--
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane_at_wandisco.com
Received on 2014-06-18 02:00:29 CEST

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.