[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: <kfogel_at_collab.net>
Date: 2003-06-25 21:00:49 CEST

Ben Collins-Sussman <sussman@collab.net> writes:
> > 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.
> Actually, this was a keyword expansion bug fixed in HEAD a couple of
> days ago. svn 0.24.2 still has the bug.
> The bug was exactly what Vincent is describing: in certain keyword
> expansion situations, $Rev$ was being accidentally expanded to the
> working-rev, rather than the last-changed-rev.

It's not clear to me that that's what Vincent was describing. I
thought he was saying that the working copy revision was at 17, and
the file's most recent commit (in the repository) was in revision 59.
If the file was also committed in revision 17, then the behavior he
describes above is expected -- no bug necessary.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 25 21:49:54 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.