-f option for subwcrev leads to a wrong "last commit revsion"

21 views
Skip to first unread message

lorenz.p...@gmail.com

unread,
Aug 31, 2020, 10:42:01 AM8/31/20
to TortoiseSVN
Hello all,

I'm experiencing an issue with the subwcrev tool. Here is the log:

Annotation 2020-08-31 115227.png


I have updated my working copy to revision 15 (incl. external). Furthermore I have a .subwcrevignore file with following content:

f3
f3/*

Now if I run subwcrev without the ignore file (subwcrev .) the output is plausible:

D:\Data\development\SvnBase>subwcrev .
SubWCRev: 'D:\Data\development\SvnBase'
Last committed at revision 15
Updated to revision 15
Unversioned items found

With the ignore file the output is still as expected:

D:\Data\development\SvnBase>subwcrev .
SubWCRev: 'D:\Data\development\SvnBase'
Last committed at revision 14
Updated to revision 15
Unversioned items found

But now comes the issue. If I run subwcrev with the -f option the last commit revision is wrong in my opinion:

D:\Data\development\SvnBase>subwcrev . -f
SubWCRev: 'D:\Data\development\SvnBase'
Last committed at revision 15
Updated to revision 15
Unversioned items found

As one can see in the log in revision 15 only the file fi8.txt has changed so the -f option should not affect the last commit revision.

Is this a bug or a feature?

Many thanks
Lorenz

Stefan

unread,
Sep 1, 2020, 10:53:49 AM9/1/20
to TortoiseSVN
the output is correct. You see, if you commit a file in a folder, that folder and all parent folders get their last-committed-rev updated as well. So ignoring a subfolder won't help.

Reply all
Reply to author
Forward
0 new messages