Rebasing topics sometimes results in empty changesets

[Craig Ozancin]

On occasion I get an 'note: created empty successor' warning when rebasing
topic branches after publishing changesets. I am sure there is a valid use
for this, but for me this is an annoyance. I prefer to not have any empty
changesets.


My first thought was that perhaps there was a configuration that would
address this for me. Sure enough, looking into the mercurial source, I
found a check for
'rewrite.empty-successor' being set to either keep (keep empty changesets)
or skip (skip empty changesets). It appears to be under the ui section. I
added the fo
llowing to my .hgrc file:



[ui]

rewrite.empty-successor = skip



Unfortunately, the next time I was doing a rebase, I still got the warning
and an empty changeset.


Has anyone else seen this or used this configuration? Is my hgrc entry
valid?

Any thoughts on this are very welcome.

Craig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20240630/b6de6977/attachment.html>