Re: Meaning of LastChangedRevision

On Wed, Jun 25, 2003 at 14:00:49 -0500, kfogel@collab.net wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
> > 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.

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.

-- 
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