summaryrefslogtreecommitdiff
path: root/open_issues/versioning.mdwn
diff options
context:
space:
mode:
authorJoshua Branson <jbranso@dismail.de>2026-04-02 21:22:41 -0400
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2026-04-15 23:54:37 +0200
commit0264e7fea77fb52b8575e837b4457c37d3a46378 (patch)
tree8d842eb945d4438e3eab04e8222154f1bf00dabe /open_issues/versioning.mdwn
parentfc7c61f7e171d9a4c964140d3e16c109e4428cc9 (diff)
delete open_issues/packaging_libpthread.mdwn.
Message-ID: <20260403012244.8302-5-jbranso@dismail.de>
Diffstat (limited to 'open_issues/versioning.mdwn')
-rw-r--r--open_issues/versioning.mdwn19
1 files changed, 0 insertions, 19 deletions
diff --git a/open_issues/versioning.mdwn b/open_issues/versioning.mdwn
index 18fb588e..ca44f61d 100644
--- a/open_issues/versioning.mdwn
+++ b/open_issues/versioning.mdwn
@@ -51,25 +51,6 @@ versioning?
There are some comments in the sources, for example `hurd/geteuids.c`: `XXX
Remove this alias when we bump the libc soname.`
-
-### IRC, freenode, #hurd, 2012-12-14
-
-[[!tag open_issue_glibc open_issue_libpthread]]
-
-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...
-
-[[glibc#execve_relative_paths]].
-
-
### `time_t` -- Unix Epoch vs. 2038
#### IRC, freenode, #hurd, 2013-12-12