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

Re: svn commit: r1089856 - /subversion/trunk/subversion/tests/cmdline/switch_tests.py

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Fri, 08 Apr 2011 13:39:03 +0100

"C. Michael Pilato" <cmpilato_at_collab.net> writes:

> On 04/08/2011 04:48 AM, Philip Martin wrote:
>> Not sure I understand. Are you saying that "copy then switch then
>> commit" should be the same as "copy then commit then switch"?
> I'm suggesting that "copy A Z; switch Z/D; commit Z" should be the same as
> "switch A/D; copy A Z; commit Z".

I still confused: "copy/switch/commit" isn't supported; one cannot
switch a copy. So is this just a roundabout way of saying that the
original test case, "switch/copy/commit", should not be supported or are
you proposing some behaviour that should be supported?

> In other words, stop treating a switch
> like a local mod. A switch isn't a local mod -- it's a client-only view
> option, kinda like a sparse directory is. Or just say, "Sorry, I can't do
> that copy, because you won't get the result you might think you'd get."

Received on 2011-04-08 14:39:37 CEST

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.