|
From: | J Decker |
Subject: | Re: [Monotone-devel] fixing old commit messages |
Date: | Tue, 17 Jun 2014 09:18:49 -0700 |
mtn comment rev [comment]
This adds a new comment to a committed revision (see Selectors). If comment is not provided, it is obtained from the Lua hook edit_comment
; 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 06/14/2014 06:32 PM, Hendrik Boom wrote:What I sometimes do is commit to a private feature branch, where I don't
> 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?
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
address@hidden
https://lists.nongnu.org/mailman/listinfo/monotone-devel
[Prev in Thread] | Current Thread | [Next in Thread] |