Re: fixing old commit messages

isn't it just as simple as adding a comment?

mtn comment rev [comment]

This adds a new comment to a committed revision (see Selectors
<http://www.monotone.ca/docs/Selectors.html#Selectors>). If comment is not
provided, it is obtained from the Lua hook edit_comment
<http://www.monotone.ca/docs/User-Defaults.html#edit_005fcomment>; the hook
is passed an empty string.

This command is a synonym for mtn cert rev comment comment.

which becomes a lot easier than any other version system...


On Tue, Jun 17, 2014 at 9:05 AM, Markus Wanner <[email protected]> wrote:

> On 06/14/2014 06:32 PM, Hendrik Boom wrote:
> > When I commit a revision, I get to write a message explaining what this
> > revision does.
> >
> > But sometines I look at the old commit messages and cringe.
> >
> > I have troubleetyping correctly, and there are often typos and worse.
> >
> > Is there any way to edit an old commit message?
>
> What I sometimes do is commit to a private feature branch, where I don't
> have to worry much about the commit message. Then "merge" the branch
> with mtn pluck, thinking harder about the message after the entire
> feature is done (testing takes a while; usually I end up having multiple
> commits in the branch or even merges from the parent branch) and then
> suspending that feature branch.
>
> Of course, you need to plan ahead for that to work. And technically it's
> not really editing the commit message, but rather adding an intermediate
> step. But one that doesn't need to be visible to others.
>
> Regards
>
> Markus Wanner
>
>
>
> _______________________________________________
> Monotone-devel mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/monotone-devel
>

_______________________________________________
Monotone-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/monotone-devel