New Message Extension

[David Soria Parra]

would be great to have hg merge prefill message.

On 2009-09-03, Yann E. MORIN <yann.morin.1998 at anciens.enib.fr> wrote:
> Adrian,
> All,
>
> On Thursday 03 September 2009 15:22:35 Adrian Buehlmann wrote:
>> cd libxy
> [--SNIP--]
>> Nope. message.txt is not here!
>
> OK.
>
>> hg mes -e  (finish the comments)
>> hg ci
>
> Which is then redundant, since hg ci will open the editor, right?
>
>> * you don't have to remember the file name ('message.txt') or location
>
> OK.
>
>> * tools can access it, due to standard location
>
> What tools?
>
>> * hg ci will present you the message, preloaded into the editor
>>   (with the usual HG: lines at the bottom). hg ci --logfile in
>>   contrast just commits without starting the editor
>
> OK.
>
> So how does it play with, say, mq?
>
> Not saying that's not usefull, but just trying to spot some corner-cases,
> to see how they can be resolved if need be.
>
> Now, I can see where it can be usefull. I usually use mq, even for a
> single change, so I can indeed pre-fill the commit message, and update
> it prior to making the change a definitive changeset. Using this
> extension would nicely replace mq in this context.
>
> Regards,
> Yann E. MORIN.
>