This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug manual/20524] strverscmp is inconsistent
- From: "peda at lysator dot liu.se" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 29 Aug 2016 14:02:30 +0000
- Subject: [Bug manual/20524] strverscmp is inconsistent
- Auto-submitted: auto-generated
- References: <bug-20524-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20524
--- Comment #5 from Peter Rosin <peda at lysator dot liu.se> ---
Created attachment 9481
--> https://sourceware.org/bugzilla/attachment.cgi?id=9481&action=edit
fix ordering in strverscmp
Ok, it was said that fixing it was not an option "at this point" since "it
is what it is". But the function has been "fixed" once, in 2009 [1], so
what is different "at this point"? And gnulib still has the old version
from pre-2009. So, everything is out of sync and just generally b0rked.
FWIW, this patch fixes it to my liking. I'm not bothering with a
changelog/signoff since I have little hope of it being applied...
The patch gets you this order:
0000 < 000 < 000! < 000a < 00 < 00! < 00a < 0001 < 001 < 0100 < 010 < 010! <
010a < 01 < 01! < 01a < 0101 < 011
[1]
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=4546646233574f321f9deedff928b980d82f4fc7
--
You are receiving this mail because:
You are on the CC list for the bug.