This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 29 Jun 2016 19:56, H.J. Lu wrote: > On Wed, Jun 29, 2016 at 6:37 PM, Mike Frysinger <vapier@gentoo.org> wrote: > > On 29 Jun 2016 11:15, H.J. Lu wrote: > >> On Tue, Jun 28, 2016 at 7:28 PM, Mike Frysinger <vapier@gentoo.org> wrote: > >> > should have a comment or two mentioning why you need to code all of > >> > these things ad-hoc > >> > > >> > also needs a manual update > >> > >> I am not sure if it needs manual update. I consider it more for glibc > >> developers than for normal end users. > > > > it needs documenting somewhere beyond the commit message. i guess we > > don't have a "hacking" page somewhere, so at least the comment in the > > source file will have to do. > > It is more than just normal "hacking". You need to look at all multiarch > implementations when experimenting and their behavior can change over > time. It is more a tool for multiarch developers. It shouldn't be used by > majority of end users. "hacking" documents shouldn't be read by the majority of end users either. throwing it in the wiki under a hacking/ifunc page sounds fine. -mike
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |