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

Re: [TSVN] feature request

From: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2005-03-09 22:43:47 CET

SteveKing wrote:
>>> In Subversion, that keyword reflects the "last committed revision"
> > Yes... We use that for all our software.
> > Makes it easy to pinpoint it in the repository should there be trouble.
> That's not true. If there's a problem, in 99% of all cases it isn't just
> in one single file but in several files. Of course, if your project only
> has one file...

The revision number is global, as you point out, & we only compile
based on a working copy that is in an updated state, thus all the
files that the final .exe/whatever depends on have been committed
prior to the most recent commit of the $Rev$'ed file, thus a checkout
of the last commit rev will give the correct depended files.

No wait.

What if there's only changes in depended files, not in the main file
containing the $Rev.

Hm, I think I see where you're going.

With most of our projects, this would be a corner case.


Thank you very much for the pointer, I'll bring it up at the next meeting.

> You can look at TSVN: we use SubWCRev to assign the revision number to
> each release.

*Sighs a bit*.
Not sure why this has to be done with a external tool.
I take it that there's a mighty good reason why there isn't a
Subversion $$ keyword that expands to the current repository revision
when an update is performed?

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Mar 9 22:44:34 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.