For tags, you ought to be able to run `git tag -a <tag name> <committish>` (`git help rev-parse` for SPECIFYING REVISIONS might help).
I'm not sure about updates/descriptions, but I would consider using `git rebase -i <last good commit>`. Then for fixing descriptions make the line say `reword …` instead of `pick …`. If you need to actually change the commit more substantially, probably `edit` is better (`git help rebase` for INTERACTIVE MODE). Note that `git rebase` in this way will require a `push --force-with-lease` to push the new commits, and it may cause some pain for anyone who has the bad commits and needs to get the re-written version. Generally the advice is to not rebase public commits; if you want to change them, though, you don't have much choice. The only alternative is to publish new commits with corrections, I think. On Sunday, October 30, 2022 at 2:14:32 PM UTC-4 Bram Moolenaar wrote: > > Update: I am waiting for test results. Slowly doing more, walking > around a bit. I managed to make CI green again, let's take that > as proof that my head is OK :-). Older commits still need updates, > description and tags. It will be good if someone can suggest the git > commands for that. > > Please also keep creating PRs, it's easier to include those than > creating a fix myself (with regression tests and the like). > > Also thanks again for all the best wishes, it helps to keep my spirit > up! > > -- > Female engineers become irresistible at the age of consent and remain that > way until about thirty minutes after their clinical death. Longer if it's a > warm day. > (Scott Adams - The Dilbert principle) > > /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ > /// \\\ > \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// > \\\ help me help AIDS victims -- http://ICCF-Holland.org /// > -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/7881ebdd-0398-4220-b3ee-3356c77d3e9fn%40googlegroups.com.
