The `--reverse` problem pops up moderately often (OK occasionally). Usually it's not doing what you expect as to _when_ the reversal is applied.
https://stackoverflow.com/questions/35379277/why-does-git-log-with-follow-and-reverse-return-only-last-commit On Friday, May 5, 2023 at 12:29:56 AM UTC+1 aalexa...@gmail.com wrote: > 0.md was moved into sub directory and now git log --reverse can't find > its commits behind it, but works without --reverse. Is it a bug or I miss > something? > > $ git log --follow -M --format=%ai "0.md" > 2023-05-04 10:25:41 +0200 > 2023-03-01 02:00:51 +0100 > 2023-03-01 02:00:21 +0100 > 2023-03-01 01:59:51 +0100 > 2023-03-01 01:59:21 +0100 > 2023-03-01 01:57:51 +0100 > 2023-03-01 01:56:51 +0100 > 2023-03-01 01:37:06 +0100 > 2022-03-07 00:56:29 +0100 > $ git log --reverse --follow -M --format=%ai "0.md" > 2023-05-04 10:25:41 +0200 > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/511d43f6-354e-439f-8208-8f90f21672fcn%40googlegroups.com.
