Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) - Create a new repository - Add a new file to the repository and commit - Create a tag $ git tag -a TagOne -m "" - Update the file and commit the change - Create a tag $ git tag -a TagTwo -m "" - List tags by committerdate: $ git tag -l --sort=committerdate (oldest tag is listed first) - List tags by reversed committerdate: $ git tag -l --sort=-committerdate (oldest tag it still listed first) What did you expect to happen? (Expected behavior) Using the minus-sign as prefix is supposed to reverse the sorting order, listing the newest item first. I expected the newest tag to be listed first What happened instead? (Actual behavior) The minus-sign was ignored, and the oldest tag was still listed first What's different between what you expected and what actually happened? I expected the newest tag to be listed first when the minus-sign was used as a prefix, but the oldest tag was still listed first. Anything else you want to add: The correct behaviour (reversing sort-order by using the minus-prefix) has been verified in version 2.11.0, 2.11.1, 2.14.2, 2.19.1, 2.19.2, 2.23.0 on CentOS 7.4 version 2.31.1 and 2.35.1 on CentOS 7.4 contains the error version 2.34.1.windows.1 contains the error Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.34.1.windows.1 cpu: x86_64 built from commit: 2ca94ab318509b3c271e82889938816bad76dfea sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 19042 compiler info: gnuc: 11.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe [Enabled Hooks]
