Merge remote-tracking branch 'dirichlet.SCHWINGE/master'

2 files changed, 37 insertions, 32 deletions

diff --git a/open_issues/glibc/0.4.mdwn b/open_issues/glibc/0.4.mdwn
deleted file mode 100644
index f864469d..00000000
--- a/open_issues/glibc/0.4.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-[[!meta copyright="Copyright © 2012, 2013 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]]
-
-Things to consider doing when bumping the glibc SONAME.
-
-
-# IRC, freenode, #hurd, 2012-12-14
-
-In context of [[packaging_libpthread]]/[[libpthread]].
-
-    <pinotree> once libc is switched internally from cthreads to pthreads (thus
-      breaking its BC), may be worth cleanup the hurd-specific exported symbols
-    <tschwinge> 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.
-    <pochu> 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...
-    <tschwinge> pochu: Oh, I have to re-read that discussion, but thanks for
-      reminding!
-
-[[!GNU_Savannah_bug 28934]], [[user/pochu]], [[!message-id
-"4BFA500A.7030502@gmail.com"]].
diff --git a/open_issues/glibc/t/tls-threadvar.mdwn b/open_issues/glibc/t/tls-threadvar.mdwn
index 7ce36f41..40d1463e 100644
--- a/open_issues/glibc/t/tls-threadvar.mdwn
+++ b/open_issues/glibc/t/tls-threadvar.mdwn
@@ -116,3 +116,40 @@ dropped altogether, and `__thread` directly be used in glibc.
 ## IRC, OFTC, #debian-hurd, 2013-09-23
 
     <youpi> yay, errno threadvar conversion success
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-05
+
+    <gg0_> youpi: any ETA for tls?
+    <youpi> gg0_: one can't have an ETA for bugfixing
+    <gg0_> i don't call them bugs if there's something missing to implement btw
+    <youpi> no, here it's bugs
+    <youpi> the implementation is already in the glibc branches in our
+      repository
+    <youpi> it just makes some important regressions
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-07
+
+    <youpi> about tls, I've made some "progress": now I'm wondering how raise()
+      has ever been working before :)
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-15
+
+    <youpi> good, reply_port tls  is now ok
+    <youpi> last but not least, sigstate
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-21
+
+    <youpi> started testsuite with threadvars dropped completely
+    <youpi> so far so good
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-24
+
+    <youpi> ok, hurd boots with full-tls libc, no threadvars at all any more
+    <gg0> \o/
+    <gg0> good bye threadvars bugs, welcome tls ones ;)
+    <youpi> now I need to check that threads can really use another stack :)