On Thursday 04 September 2008 00:52:08 you wrote: > We cannot take this patch, as the gnulib strverscmp function is meant to be > a substitute for the glibc function of the same name. (Sorry, the doc was > not clear about it until today.) This means, gnulib's strverscmp needs to > behave the same as glibc's strverscmp. > > If you want a behaviour change of gnulib's strverscmp, it needs to be > accepted by glibc first. But I think, Jakub Jelinek and Ulrich Drepper > already rejected such a proposal. > > You are welcome to propose a new, different function for gnulib, though. Well, what about new gnulib function strverscmp2(), which would be original strverscmp() patched by proposed patch? Particular coreutils utilities could then choose between strverscmp() and strverscmp2().
Kamil
