Subwcrev's last commit revision is sometimes wrong (in combination with .subwcrevignore)

[Lorenz Prochaska]

Hello all,

In my opinion subwcrev does not always get the "last commit revision" right.

Let's start with my repository log:

Revision: 18
Author: Lorenz
Date: Monday, 31 August 2020 12:52:29
Message:
new feature
----
Modified : /base/f2/nf2.txt

Revision: 17
Author: Lorenz
Date: Monday, 31 August 2020 12:51:35
Message:
deleted obsolete file
----
Deleted : /base/f1/fi3.txt

Revision: 16
Author: Lorenz
Date: Monday, 31 August 2020 10:54:02
Message:
twerk
----
Modified : /base/f1/fi3.txt

Revision: 15
Author: Lorenz
Date: Monday, 31 August 2020 10:50:34
Message:
bugfix
----
Modified : /base/f3/fi8.txt

Revision: 14
Author: Lorenz
Date: Monday, 31 August 2020 10:48:23
Message:
new file added again
----
Added : /base/f2/nf2.txt

Revision: 13
Author: Lorenz
Date: Monday, 31 August 2020 10:47:49
Message:
new file added
----
Added : /base/f3/nf1.txt

----------------------------------------------------------------------------------------------------------

I updated my working copy to revision 18. I added a .subwcrevignore file with following content:

f2

f2/*

If I run subwcrev the output says that the last commit revision is 15 which seems to be wrong as there had been changes to files in directory f1 in revision 17 and 16. Why are those changes ignored?

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

Am I missing something or is this a bug?

Many thanks

Lorenz