summaryrefslogtreecommitdiff
path: root/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2013-01-08 21:34:29 +0100
committerThomas Schwinge <thomas@codesourcery.com>2013-01-08 21:43:11 +0100
commitcd42b6144bf707fa38555bc06e267bb16db011f5 (patch)
treeddebd4ae1c845bd062261b4335a9ab7a969a3c89 /open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
parenta91114fc89dd554494801349e57bd5d29454a8b1 (diff)
parente66cb01b99b60f9483de2425bca3bb104bcc9ae8 (diff)
Merge remote-tracking branch 'fp/master'
Diffstat (limited to 'open_issues/libmachuser_libhurduser_rpc_stubs.mdwn')
-rw-r--r--open_issues/libmachuser_libhurduser_rpc_stubs.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn b/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
index 57eb403d..80fe36f8 100644
--- a/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
+++ b/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
@@ -113,3 +113,11 @@ License|/fdl]]."]]"""]]
out?
<tschwinge> pinotree: That discussion has not yet come to a conclusion, I
think. (I'd say: yes.)
+
+
+# IRC, freenode, #hurd, 2012-12-17
+
+ <pinotree> what was the idea about using the rpc stubs currently in
+ libmachuser and libhurduser? should they be linked to explicitly, or
+ assume libc brings them?
+ <braunr> pinotree: libc should bring them