sort entries numerically
Hi,
is there any chance to have "1.8" before "1.10" in an output like the following :
...
From https://code.wireshark.org/review/wireshark
52fe0aa..b69642d master -> origin/master 460db8a..540f061 master-1.10 -> origin/master-1.10 25bb29a..5741a40 master-1.12 -> origin/master-1.12
4ee4fc11..97898a2 master-1.8 -> origin/master-1.8
Signature · 1 line
Toralf
Quoted 8 lines · Toralf Förster
is there any chance to have "1.8" before "1.10" in an output like the following :
...
From https://code.wireshark.org/review/wireshark52fe0aa..b69642d master -> origin/master 460db8a..540f061 master-1.10 -> origin/master-1.10 25bb29a..5741a40 master-1.12 -> origin/master-1.124ee4fc11..97898a2 master-1.8 -> origin/master-1.8
I don't find anything about it in git branch man page. However there's always:
git <command> | sort -d -r
as a workaround.
Signature · 5 lines
Med vänlig hälsning Fredrik Gustafsson tel: 0733-608274 e-post: [email protected]
Quoted 10 lines · Toralf Förster
Hi,
is there any chance to have "1.8" before "1.10" in an output like the following :
...
From https://code.wireshark.org/review/wireshark52fe0aa..b69642d master -> origin/master 460db8a..540f061 master-1.10 -> origin/master-1.10 25bb29a..5741a40 master-1.12 -> origin/master-1.124ee4fc11..97898a2 master-1.8 -> origin/master-1.8
git-tag supports version sorting. Not sure if it should be default sorting order in these listings (from fetch and push?). Maybe we could have a config key for default sorting order.
Signature · 1 line
Duy