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

Re: Feature request: SubWCRev if not inside a working copy

From: Gingko <from_tigris_at_nospam.homelinux.org>
Date: Tue, 20 Oct 2009 07:56:00 +0200

----- Original Message -----
From: "Ron Wilson" <ronw.mrmx_at_gmail.com>
To: <users_at_tortoisesvn.tigris.org>
Sent: Monday, October 19, 2009 11:25 PM
Subject: Re: Feature request: SubWCRev if not inside a working copy

> Why do you need a parallel working copy? If you want to discard
> changes, you can simply revert them.

Because I commonly maintain several different changes, often in the same
file, that (nearly always) I do not want to commit at the same time.
How can I (easily !) revert a change in a file without also revert all other
changes in the same file ?

> 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.

I currently nearly do that, by just adding "if errorlevel 1 exit 0" after
the SubWCRev call for clearing and ignoring the return code and have all the
rest of the project still running.
But I don't like that : what about getting a return code for another kind of
error ?

> 2. You could use "Keyword Substitution" instead of SubWCRev. See:
> http://svnbook.red-bean.com/en/1.5/svn.advanced.props.special.keywords.html

Keyword substititution works on file basis, not on directory basis. See
"Where's $GlobalRev$?" note in the page you quote.

Also, it needs to update the working copy after commit for getting the
change. As stated in this same page : "Keep in mind that keyword expansion
is a client-side operation, and your client “knows” only about changes that
have occurred in the repository when you update your working copy to include
those changes. If you never update your working copy, your keywords will
never expand to different values even if those versioned files are being
changed regularly in the repository."

Also, due to the syntax of the Keyword Substitution system, I don't know how
I can write this kind of thing in a C/C++ header file :


I would expect to get something like :

#define CURRENT_REVISION 12345

Whereas I will actually get :

#define CURRENT_REVISION $Rev: 12345 $

Which is nearly unusable.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-20 07:56:12 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.