On 2022-10-28, Bram Moolenaar wrote:
> Strange that this went missing. I'll add it now, please suggest a git
> command for more info on the commit if needed.
I understand your frustration with git. Here are a couple of
commands I use to examine commits.
To see the commit messages in a pager, including the names of the
affected files:
$ git log --name-only --decorate
To see side-by-side diffs of the changes between two commits, for
example, between the commit with the tag v9.0.0805 and its
predecessor:
$ git difftool v9.0.0805^..v9.0.0805
You can specify any two commits by their tags, by their commit
hashes, or by either of those with modifiers such as ^ to indicate
a parent.
The best way to fix a bad commit really depends on the situation and
on what has been pushed. It's generally difficult to change
anything already pushed. In my limited experience, the safest way
to make a change is to create a new commit that contains the code
the way you want it, including any reversions, and commit and push
that. Anything fancier than that, that you don't understand well,
can easily lead to mistakes and more frustration.
HTH,
Gary
--
--
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/20221028180428.GD14398%40phoenix.
