absorb: clarify the reason for not finding changesets to modify
I'm used to pushing to non-publishing repos, so this was the last thing I
thought to check.
--- a/hgext/absorb.py Wed Sep 05 09:36:31 2018 -0700
+++ b/hgext/absorb.py Tue Sep 04 20:48:22 2018 -0400
@@ -917,7 +917,7 @@
'be analysed\n')
% limit)
if not stack:
- raise error.Abort(_('no changeset to change'))
+ raise error.Abort(_('no mutable changeset to change'))
if targetctx is None: # default to working copy
targetctx = repo[None]
if pats is None:
--- a/tests/test-absorb.t Wed Sep 05 09:36:31 2018 -0700
+++ b/tests/test-absorb.t Tue Sep 04 20:48:22 2018 -0400
@@ -18,7 +18,7 @@
Do not crash with empty repo:
$ hg absorb
- abort: no changeset to change
+ abort: no mutable changeset to change
[255]
Make some commits:
@@ -225,7 +225,7 @@
$ echo 2 >> m1
$ echo 2 >> m2
$ hg absorb
- abort: no changeset to change
+ abort: no mutable changeset to change
[255]
$ hg revert -q -C m1 m2