From 51c95fc11727532e3b0d98c8470a6b60907a0680 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 8 Jan 2013 21:31:31 +0100 Subject: IRC. --- open_issues/glibc/0.4.mdwn | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 open_issues/glibc/0.4.mdwn (limited to 'open_issues/glibc') diff --git a/open_issues/glibc/0.4.mdwn b/open_issues/glibc/0.4.mdwn new file mode 100644 index 00000000..a8892876 --- /dev/null +++ b/open_issues/glibc/0.4.mdwn @@ -0,0 +1,28 @@ +[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!tag open_issue_glibc open_issue_libpthread]] + + +# IRC, freenode, #hurd, 2012-12-14 + +In context of [[packaging_libpthread]]/[[libpthread]]. + + once libc is switched internally from cthreads to pthreads (thus + breaking its BC), may be worth cleanup the hurd-specific exported symbols + pinotree: Yes. If you already have ideas about what to clean + up, feel free to add a new page or a section on open_issues/glibc. + we're gonna break backwards compatibility in glibc on hurd? that + could be the perfect moment to fix the /dev/fd/N problem without adding + new RPCs, though we'd probably have to break backwards-compatibility in + the exec server IIRC... + pochu: Oh, I have to re-read that discussion, but thanks for + reminding! + pochu: Won't happen today or tomorrow, but "sometime". -- cgit v1.2.3