How can I edit an older revision’s message to more correctly describe its changes?
How can I edit an older revision’s message to more correctly describe its changes?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How can I edit an older revision’s message to more correctly describe its changes?
You cannot edit the commit message of an old revision without changing the revision id of the modified revision and all its descendants.
Well… technically you can, if you try hard enough, but the technical term for the result is “corrupt repository”. A repository in bzr is a replica of a distributed database of revisions, and if all replicas don’t agree on the content of a revision, you have an integrity violation. Meaning, all bets are off, and the system will actively try to detect such situations and refuse to work.
To modify the commit message of the last revision in a branch, you can use “bzr uncommit”, followed by “bzr commit” with the new commit message.
To modify the commit message of an older revision, you get a branch whose last revision you want to modify, use “uncommit” then “commit”, and re-attach the subsequent revisions using “bzr rebase” or “bzr replay” (from the “rewrite” plugin).
In every case, that will produce a branch which is considered “divergent” from the one you had initially. If the initial branch was published, your original revisions can come back to cause painful merges, history pollution, and generally haunt you.