Any way to prevent Evolve's `metaedit` from opening the message?
Matt Harbison
matt_harbison at yahoo.com
Sun Apr 9 02:57:19 UTC 2023
> On Apr 7, 2023, at 1:56 PM, Marcos Cruz <evolve-testers-list at programandala.net> wrote:
>
> Faheem Mitha escribió/skribis/wrote/scrit (2023-04-07T22:18:48+0530):
>
>> Yes, normally metaedit is intended to edit the existing commit message.
>> Hence it's natural to open an editor. What's the problem with that?
>
> I'm converting my last Fossil repos to Mercurial.
>
> The other day I had to fix the author of 287 commits that lacked email
> because of an old unnoticed misconfiguration in the Fossil repo, which
> has a GitHub mirror.
>
> I wrote a simple shell loop in order to change all of the commits in a
> single step… but I had to close the Neovim editor 287 times instead :)
> (I did a pause to check the docs and do some tests, but it seemed clear
> that there was no solution, so I finished the 287 manual non-editions…)
>
> I've found a second repo with ca. 90 commits without user email, so I
> prefered to ask, just in case.
If you haven’t finished the conversion yet, you might consider customizing the convert extension, to allow you to update the fields as the conversion proceeds:
https://www.mercurial-scm.org/wiki/ConvertExtension#Customization
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20230408/3e031a57/attachment.html>
More information about the Evolve-testers
mailing list