IIUC, to correct a typo in a commit message for a commit already published, you have to add a new commit backing out the "wrong" one, the a second new commit equal to the one backed out (the one with the "wrong" commit message) but with the correct commit message. At least that's how it is with Mercurial, where commit history, including commit messages, is "cast in bronze" and can't be modified, only added to. I'm less sure about git. Not sure if it's worth it anyway.
Best regards, Tony. On Mon, Feb 29, 2016 at 5:16 AM, h_east <[email protected]> wrote: > Hi Bram, > > 2016-2-22(Mon) 7:03:23 UTC+9 Bram Moolenaar: >> Patch 7.4.1384 >> Problem: It is not easy to use a set of plugins and their dependencies. >> Solution: Add packages, ":loadopt", 'packpath'. > > I found typo in the commit message. > > s/:loadopt/:loadplugin/ > > -- > Best regards, > Hirohito Higashi (a.k.a h_east) > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
