Hello, Agustina Arzille, on Sun 03 Apr 2016 22:40:52 -0300, wrote: > >You can submit that patch to the libc-al...@sourceware.org mailing list > >(explaining the rationale etc. alongside), putting rol...@hack.frob.com > >and this bug-hurd@gnu.org list in Cc. And we can commit the patch to > >the debian libc in parallel. > > Done. Although, I had to use a different mail address for Roland, because > bugzilla wouldn't let me otherwise. Oh well, hope it isn't an issue. > > Anyway, here's the bug report for glibc: > > https://sourceware.org/bugzilla/show_bug.cgi?id=19903
Mmm, in my memory entries in bugzilla don't get as much attention as patches submitted to libc-alpha. Please do as I said: send a complete patch to the libc-alpha mailing list, with roland in Cc, so he explictly gets the mail with the code inline. Doing things another way means more time from him, and thus much lower probability of getting an answer. Samuel
