Why do you need a parallel working copy? If you want to discard
changes, you can simply revert them.
That said, there are alternatives.
1. You could use a script to export working copy with an already
generated header file. The script would run SubWCRev in the working
copy, then copy the generated header file to your parallel copy.
2. You could use "Keyword Substitution" instead of SubWCRev. See:
On Mon, Oct 19, 2009 at 2:50 PM, Gingko
> ----- Original Message -----
> From: "Simon Large" <simon.tortoisesvn_at_googlemail.com>
> To: <users_at_tortoisesvn.tigris.org>
> Sent: Monday, October 19, 2009 3:10 PM
> Subject: Re: Feature request: SubWCRev if not inside a working copy
>> The sole purpose of SubWCRev is to extract version information from a
>> working copy. Why would you want to use it on something which is not a
>> working copy? I don't understand your need to export projects (make it
>> unversioned) and then pretend that it is versioned.
> I generally use SubWCRev from within a script (actually most of the time
> from a Visual Studio project rule, which is a kind of script).
> That way, I can generate a C or C++ header file from a template file.
> I suppose that calling SubWCRev from a script is a probably a very common
> usage of it.
> On another hand, whereas the whole main project is maintained inside a
> versioned directory, it is very common that I make an unversioned copy of
> this same directory, side by side in a common root directory, that I use
> for testing changes that I am not sure if I will decide to commit or not.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-19 23:25:46 CEST