From 04e9cc0f37dc03b334b0a5cc2896d4b41245f4c1 Mon Sep 17 00:00:00 2001
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Wed, 18 Feb 2015 00:58:19 +0100
Subject: Revert "update for rename of open_issues/clock_gettime.mdwn to
 service_solahart_jakarta_selatan__082122541663/clock_gettime.mdwn"

This reverts commit 1d66e99de816da3149a82fcd91d1915c0055178f.
---
 service_solahart_jakarta_selatan__082122541663/select.mdwn | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/service_solahart_jakarta_selatan__082122541663/select.mdwn b/service_solahart_jakarta_selatan__082122541663/select.mdwn
index 07e2764b..3e36519c 100644
--- a/service_solahart_jakarta_selatan__082122541663/select.mdwn
+++ b/service_solahart_jakarta_selatan__082122541663/select.mdwn
@@ -651,7 +651,7 @@ IRC, unknown channel, unknown date:
     <youpi> well, I'd say gnumach could grow a nanosecond-precision time value
     <youpi> e.g. for clock_gettime precision and such
 
-[[service_solahart_jakarta_selatan__082122541663/clock_gettime]].
+[[clock_gettime]].
 
     <braunr> so you would prefer me adding the time_spec_t time to gnumach
       rather than the hurd ?
-- 
cgit v1.2.3