How to edit incorrect commit message in Mercurial? [duplicate]

by

Update: Mercurial has added --amend which should be the preferred option now.

You can rollback the last commit (but only the last one) with hg rollback and then reapply it.

Important: this permanently removes the latest commit (or pull). So if you’ve done a hg update that commit is no longer in your working directory then it’s gone forever. So make a copy first.

Other than that, you cannot change the repository’s history (including commit messages), because everything in there is check-summed. The only thing you could do is prune the history after a given changeset, and then recreate it accordingly.

None of this will work if you have already published your changes (unless you can get hold of all copies), and you also cannot “rewrite history” that include GPG-signed commits (by other people).

More Related Contents:

  1. Mercurial Subrepos – How do you create them and how do they work?
  2. Mercurial for Beginners: The Definitive Practical Guide
  3. Named Branches vs Multiple Repositories
  4. Mercurial — revert back to old version and continue from there
  5. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  6. Mercurial: How to ignore changes to a tracked file
  7. Source Control – Distributed Systems vs. Non Distributed – What’s the difference?
  8. Mercurial: Merging one file between branches in one repo
  9. What is the difference between hg forget and hg remove?
  10. Mercurial undo last commit
  11. Distributed Version Control Systems and the Enterprise – a Good mix? [closed]
  12. Why is a 3-way merge advantageous over a 2-way merge?
  13. Git and Mercurial – Compare and Contrast
  14. Using IPython / Jupyter Notebooks Under Version Control
  15. What is the Difference Between Mercurial and Git?
  16. Should I store generated code in source control
  17. Source control vs. Revision Control?
  18. how to ignore files in kiln/mercurial using tortoise hg “that are part of the repository”
  19. What are the relative strengths and weaknesses of Git, Mercurial, and Bazaar? [closed]
  20. Is there a way to keep Hudson / Jenkins configuration files in source control?
  21. Comparison between Centralized and Distributed Version Control Systems [closed]
  22. Can you “ignore” a file in Perforce?
  23. How often to commit changes to source control? [closed]
  24. Do you continue development in a branch or in the trunk? [closed]
  25. What makes some version control systems better at merging?
  26. Mercurial: how to amend the last commit?
  27. Store password in TortoiseHg
  28. How to find untracked files in a Perforce tree? (analogue of svn status)
  29. Code version change “rules” [closed]
  30. What is the difference between all the different types of version control?

Leave a Comment