Change number display changeset about scm-manager

[pfeuffer]

Hi @nikobcs ,

the counter you are missing is a number, that differs from instance to instance of a single repository. So number 42 on your PC could be number 23 on the server. Therefore we did not think that this would be of great value (and currently this cannot be configured). I'd be interested in the use case you would like to have this number for.

Thanks
René

[nikobcs]

Hi @pfeuffer,
It’s not entirely clear why the version number can be different on the server and on the client?

Very complex (however reproduceable) calculations.
At some moment we see difference in results.
Problem: find the commit leaded to such change in result to juge for correctness
Our solution (aka bisection):
• sync to some old revisision, reproduce "old" result.
• sync to head. reproduce "new" result.
• sync to "midpoint". get result. If result is same as "old" – continue to search in upper (newer) halve, otherwise continue to search in lower (older) halve.
Running sequence of Revision is very convinient for such bisect algorithm.
Of course the procedure could be automated, however it is not an easy task because of infrastructure.

[pfeuffer]

Hi @nikobcs ,

I know this feature from Git and I love it. And as far as I get it, there is no need to change the way you are working in a relevant way. The only important point you need to consider is, that revision numbers are not necessarily the same for revisions on all clones. See this excerpt from the hg documentation:

So, your workflow must not rely on the revision number, though you can use it to iterate the commits in your clone. To later identify a revision, you always have to use the hash code.

Hope this helps :-)
René

[nikobcs]

I understand. Thank you for your help!
Have a good day!