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

Re: workaround for $WorkingRevision$ ?

From: Bill Comisky <bcomisky_at_pobox.com>
Date: 2003-06-18 21:14:02 CEST

On Wed, 18 Jun 2003, Ben Collins-Sussman wrote:

> Bill Comisky <bcomisky@pobox.com> writes:
> > I have a repository of source code for an interpreted (not-compiled)
> > language, in this case Matlab m-files. It's very useful for me to be able
> > to record the "working revision" in output files generated by this code.
> > For example if an incompatiblity in the output file format is introduced,
> > I can determine what revision it was created with and backtrack.
> >
> > I've been reading the archives about a $WorkingRevision$ keyword (which
> > would be perfect for what I want) [...]
> Let's back up a step. I don't understand why $LastChangedRevision$ is
> insufficient for solving your problem.
> I mean, if one generated file claims to have been produced by "working
> revision 170", and another one by "working revision 171", does that
> *mean* anything? Most likely, revs 170 and 171 of the m-file are
> completely identical.
> $LastChangedRevision$ is the true "version" of the file. Isn't that
> what you care about?

It's not a particular file I'm interested in. It's what the HEAD revision
number was when the working copy was last updated (or checked out/exported
as appropriate). Maybe I confused the issue by mentioning my "output
file" example. Those aren't versioned files, but IO files generated by
users running the code. I'd like to record the revision number of the
code that generates the file, in that file AT RUNTIME. Anyone using a
mixed-revision wc is out of luck.

Suffice to say I'd like to have my code "know" somehow what the HEAD
revision number was when the wc was last updated/checked out/exported.

Am I making sense yet? :)


Bill Comisky
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 18 21:14:56 2003

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.