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:
The problem I've described is that the value of $LastChangedRevision$
> If by '"current" revision' you mean the revision your working copy
Yes, just before the commit.
> then there is no way a working copy file at revision 17 can have a
This is currently not true (the bug, I assume). For instance:
ay:~/wd/www> svn -v list Makefile
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
So, both commit and checkout give wrong values.
> I was also assuming that "the file is committed to revision 59" means
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.orgReceived 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.