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

Re: Meaning of LastChangedRevision

From: Vincent Lefevre <vincent+svn_at_vinc17.org>
Date: 2003-06-26 00:25:35 CEST

On Wed, Jun 25, 2003 at 14:57:31 -0500, kfogel@collab.net wrote:
> Vincent Lefevre <vincent+svn@vinc17.org> writes:
> > I use the Id keyword in files and the LastChangedRevision component
> > (the number after the file name) is quite strange: in general, it
> > seems to be the revision where the file has changed, e.g. if the
> > "current" revision is 17 and the file is committed to revision 59,
> > then LastChangedRevision will be 17, not 59. But after a new checkout
> > of the repository (this sometimes happens), LastChangedRevision will
> > no longer be 17, but the last current revision or something like that.

The problem I've described is that the value of $LastChangedRevision$
can be different for a same version of a file (it depends on the
operations that have been performed).

> If by '"current" revision' you mean the revision your working copy
> is at,

Yes, just before the commit.

> then there is no way a working copy file at revision 17 can have a
> LastChangedRevision of 59. It could have a LastChangedRevision of
> anything up to and including 17, but not higher.

This is currently not true (the bug, I assume). For instance:

ay:~/wd/www> svn -v list Makefile
P 20 lefevre 5122 Jun 19 01:39 Makefile
ay:~/wd/www> grep Id Makefile
# $Id: Makefile 71 2003-06-18 23:39:56Z lefevre $

because I checked out revision 71. But I suppose that one should have had:

# $Id: Makefile 20 2003-06-18 23:39:56Z lefevre $

Another example: I have another file I committed when the current
revision was 100 and the commit produced revision 102. The $Id$
keyword says rev. 100 and 'svn list -v' says rev. 102. Again, a
mismatch (I suppose that 102 is the correct value).

So, both commit and checkout give wrong values.

> I was also assuming that "the file is committed to revision 59" means
> that in the *repository*, the last time the file was changed was in
> revision 59 (which is much later than 17, the revision of your working
> copy).

Yes, it is normal that it is no longer 17, but it isn't 59 either!

Vincent Lefèvre <vincent_at_vinc17.org> - Web: <http://www.vinc17.org/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 26 00:26:31 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.