Menu
▾
▴
#44 Note links to wrong revision two ways
There is a known issue with hop note, in that it gets the
revision out of cvs and increments it, instead of using
the current revision. This is easily fixable.
There's another issue, though. The revision it gets is the
result of a cvs log -h. This gets the latest revision in
CVS. In our case, the revision being reviewed is often
not the latest revision.
Say you're reviewing a change with version 1.1 of a file,
but there are two more changes already closed. Note
gets the latest revision number in cvs, which is 1.3, and
uses that.
I know that ideally point is supposed to review the
changes, make notes, pass them, and then the
developers apply them. But that almost never happens
here. We have way too many changes. It's a permanent
backlog. People are very rarely able to wait until point
has reviewed a file before using it again. It would be
better if it got the revision number via cvs status.