----- Original Message -----
From: "Andy Levy" <andy.levy_at_gmail.com>
Sent: Tuesday, October 20, 2009 8:27 PM
Subject: Re: Feature request: SubWCRev if not inside a working copy
> On Tue, Oct 20, 2009 at 14:21, Gingko <from_tigris_at_nospam.homelinux.org>
>> ----- Original Message -----
>> From: Daniel Becroft
>> To: users_at_tortoisesvn.tigris.org
>> Sent: Tuesday, October 20, 2009 8:09 AM
>> Subject: Re: Feature request: SubWCRev if not inside a working copy
>>> If that's the case, why can you not simply check-out multiple working
>>> copies, rather than using 'unversioned' copies? If it's a bandwidth
>>> then you can copy an existing working copy entirely, then revert all
>>> in the copy.
>> Because this makes a clear difference between where I make tests and
>> where I
>> make "official" changes, and also this helps avoiding committing from the
>> wrong working copy by mistake.
> Why are you not creating "experimental" branches in your repository?
Because I want to decide what I share with project's other members and what
I do not share.
Anyway this is running out of the subject.
Maybe in the future I will decide to make multiple working copies and/or
experimental branches in the repository and maybe I will not do that.
But the fact that SubWCRev cannot run outside working copies without
returning an error code breaking scripts from which it is called is not
important enough for being the reason of my decision.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-20 22:46:37 CEST