Source

histedit / README

Diff from to

File README

 Interactive history editing for Mercurial.
 
 **Warning**: ``histedit`` alters history! It probably won't destroy your data,
-but that chance exists. You should *never* edit already-published history. 
+but that chance exists. You should *never* edit already-published history.
 Caveat Emptor. (You may want to use the --outgoing option to prevent editing
 pushed history, though the changes may already be in another repository.)
 
-**Warning 2**: If you ``drop`` a change, it's *gone* **forever** (unless you 
+**Warning 2**: If you ``drop`` a change, it's *gone* **forever** (unless you
 passed ``--keep``). You've been warned!
 
 With this extension installed, Mercurial gains one new command: histedit. Usage
  #  e, edit = use commit, but stop for amending
  #  f, fold = use commit, but fold into previous commit
  #  d, drop = remove commit from history
+ #  m, mess = edit message without changing commit content
  #
  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
 In this file, lines beginning with ``#`` are ignored. You must specify a rule
-for each revision in your history. For example, if you had meant to add gamma 
-before beta, and then wanted to add delta in the same revision as beta, you 
+for each revision in your history. For example, if you had meant to add gamma
+before beta, and then wanted to add delta in the same revision as beta, you
 would reorganize the file to look like this::
 
  pick 030b686bedc4 Add gamma
  #  e, edit = use commit, but stop for amending
  #  f, fold = use commit, but fold into previous commit
  #  d, drop = remove commit from history
+ #  m, mess = edit message without changing commit content
  #
  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
  o  0   d8d2fcd0e319   2009-04-27 18:04 -0500   durin42
       Add alpha
 
-Note that ``histedit`` does *not* remove any revisions (even its own temporary 
-ones) until after it has completed all the editing operations, so it will 
+Note that ``histedit`` does *not* remove any revisions (even its own temporary
+ones) until after it has completed all the editing operations, so it will
 probably perform several strip operations when it's done. For the above example,
 it had to run strip twice. Strip can be slow depending on a variety of factors,
 so you might need to be a little patient. You can choose to keep the original
 
 The ``edit`` operation will drop you back to a command prompt, allowing you to
 edit files freely, or even use ``hg record`` to commit some changes as a separate
-commit. When you're done, any remaining uncommitted changes will be committed as 
-well. When done, run ``hg histedit --continue`` to finish this step. You'll be 
+commit. When you're done, any remaining uncommitted changes will be committed as
+well. When done, run ``hg histedit --continue`` to finish this step. You'll be
 prompted for a new commit message, but the default commit message will
 be the original message for the ``edit`` ed revision.
 
-If ``histedit`` encounters a conflict when moving a revision (while handling 
-``pick`` or ``fold``), it'll stop in a similar manner to ``edit`` with the 
-difference that it won't prompt you for a commit message when done. If you
-decide at this point that you don't like how much work it will be to rearrange
-history, or that you made a mistake, you can use ``hg histedit --abort`` to 
-abandon the new changes you have made and return to the state before you attempted
-to edit your history.
+The ``message`` operation will give you a chance to revise a commit
+message without changing the contents. It's a shortcut for doing
+``edit`` immediately followed by `hg histedit --continue``.
+
+If ``histedit`` encounters a conflict when moving a revision (while
+handling ``pick`` or ``fold``), it'll stop in a similar manner to
+``edit`` with the difference that it won't prompt you for a commit
+message when done. If you decide at this point that you don't like how
+much work it will be to rearrange history, or that you made a mistake,
+you can use ``hg histedit --abort`` to abandon the new changes you
+have made and return to the state before you attempted to edit your
+history.
 
 ============
 --outgoing