tree 74dcfa1966e082b22f78c4f8f9abc557f62f0d04
parent cf96f0926353c4b29d4a00974f85ddb980a2d683
author Ben Rohlfs <brohlfs@google.com> 1653905170 +0200
committer Ben Rohlfs <brohlfs@google.com> 1653992568 +0200

Rename `currentPatchNum` to just `patchNum`

This is more consistent with the rest of the code base. `patchNum` is
always the current choice of patchset by the user. `latestPatchNum` is
used for describing the highest existing patchset number, also very
consistent. `currentPatchNum` was just confusing, because you were
wondering, if there is a third meaningful patchset number, or whether
it is the same as `patchNum` or rather `latestPatchNum`.

Release-Notes: skip
Change-Id: I6019f9adcc0db6d73e7b23e2bc35f19fb786f8c0