Vincent Lefevre <vincent+svn@vinc17.org> writes:
> I understand that a same version of a file exists in several revisions.
> But even if I check out some revision, I do not expect the $Rev$ keyword
> to always be that revision. I want it to be the *first* revision for
> which this version of the file exists, a bit like the behavior of the
> $Date$ keyword (one gets the date of the first revision containing this
> version of the file, even if one checks out a later revision).
>
> I think that this corresponds to the bug mentioned by Ben.
Now I'm confused :-).
The behavior you described in your original mail is consistent with
the behavior you say you want (above), and behavior you say you want
is also the behavior we want.
Your original post said this:
> 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.
If by '"current" revision' you mean the revision your working copy is
at, 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.
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).
Did I misunderstand you?
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 25 22:46:41 2003