On 2019-02-19 20:37:01 +0000, Scott Bloom wrote:
> Thanks.. That is exactly what Im looking for!
Even if this is implemented, there's an issue with all these keywords
with path/URL information in them: the expanded path is the one of the
revision that last changed the file, not the current one! For instance,
if the file is in a directory that has been renamed and the file hasn't
changed since, then the expanded path will become obsolete (mentioning
the old directory name).
For instance, after a "svn mv dir newdir" and commit:
$ cat newdir/file
$PathRev: dir/file, r2 $
$ svn pl -v newdir/file
Properties on 'newdir/file':
$ svn info newdir/file
Working Copy Root Path: /home/vlefevre/tmp/svntest/wc
Relative URL: ^/newdir/file
Repository Root: file:///home/vlefevre/tmp/svntest/foo
Repository UUID: c461bb2a-7775-4e63-8d8c-e8e280081214
Node Kind: file
Last Changed Author: vlefevre
Last Changed Rev: 2
BTW, the documentation in
The file's path, relative to the repository root.
The file's path of the revision given by %r, relative to the
AFAIK, "of the revision given by %r" applies to all format codes.
Vincent Lefèvre <email@example.com> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Received on 2019-02-28 16:44:23 CET