I think you can get bitten once and you learn how valuable a trunk with
append_revisions_only set is. The case you outline above can only occur
with a branch shared between several devs that doesn't try to preserve
a linear history on that branch.
Trying to revnos in such a context is bound to fail.
As a UI rule, we don't show revids until required, I think this patch deserves
the exception (but it's activated by -v so one can argue that it's required :)
since some branches doesn't have a linear history, but not
displaying the revno at all, will be a violation of this rule.
I think you can get bitten once and you learn how valuable a trunk with revisions_ only set is. The case you outline above can only occur
append_
with a branch shared between several devs that doesn't try to preserve
a linear history on that branch.
Trying to revnos in such a context is bound to fail.
As a UI rule, we don't show revids until required, I think this patch deserves
the exception (but it's activated by -v so one can argue that it's required :)
since some branches doesn't have a linear history, but not
displaying the revno at all, will be a violation of this rule.