Pretty much the title: the commit messages end up applied in the complete reverse order of what they should be.
Grec points to the correct commit hashes during the process, but when I check the new commit history, what should've been the latest commit's message is now the first commit of the repo's message.
I believe this is an issue with how git-filter handles the order of commits, though I may be wrong.
Pretty much the title: the commit messages end up applied in the complete reverse order of what they should be.
Grec points to the correct commit hashes during the process, but when I check the new commit history, what should've been the latest commit's message is now the first commit of the repo's message.
I believe this is an issue with how git-filter handles the order of commits, though I may be wrong.