summaryrefslogtreecommitdiff
path: root/open_issues/clock_gettime.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2013-04-07 18:18:44 +0200
committerThomas Schwinge <tschwinge@gnu.org>2013-04-07 18:18:44 +0200
commit6c7d45e4631784d0e077e806521a736da6b0266e (patch)
treef9d3e9ed304e8cdbf72fc77c135781eb49990f6a /open_issues/clock_gettime.mdwn
parentf8ed211a4da23edf469089254b3dace9479bf11f (diff)
IRC.
Diffstat (limited to 'open_issues/clock_gettime.mdwn')
-rw-r--r--open_issues/clock_gettime.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/open_issues/clock_gettime.mdwn b/open_issues/clock_gettime.mdwn
index 83ad81e8..b2fbf3e0 100644
--- a/open_issues/clock_gettime.mdwn
+++ b/open_issues/clock_gettime.mdwn
@@ -184,3 +184,12 @@ In context of [[select]].
<braunr> do you want to make the changes yourself or should i add a new
branch ?
<youpi> and we'll make that a 64bit struct when we have a64bit userland
+
+
+# IRC, freenode, #hurd, 2013-04-06
+
+ <tschwinge> pinotree: You had once been working on adding nsec-procision
+ timestamps to GNU Mach's maptime interface (or what the name is). Is
+ that blocked on something or just waiting to be continued?
+ <pinotree> blocked on me needing to learn more the proper way to do
+ "atomic" update of the struct with time :)