1 files changed, 27 insertions, 27 deletions

diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn
index 2b518b06..fd6c6aad 100644
--- a/user/scolobb.mdwn
+++ b/user/scolobb.mdwn
@@ -71,39 +71,39 @@ For documentation, see [[hurd/translator/unionmount]].
 
 (Dates in brackets show the approximate deadline)
 
-* **Learn texinfo.** (Fri, 5 Jun) In order to produce canonical
+* **Learn texinfo.** *(5 Jun)* In order to produce canonical
   documentation I will have to learn the texinfo documentation format.
 
-* **Write documentation for `unionmount`.** (Fri, 5 Jun) The basic
+* **Write documentation for `unionmount`.** *(5 Jun)* The basic
   unionmount functionality being finished, it has to be documented
   properly, lest it should lag behind and remain unfinished
   eventually.
 
-* **Write documentation for `unionfs`.** (Fri, 5 Jun) `unionfs`
-  is not exactly well-documented at the moment, the only help being
-  provided by the comments in the sources. The goal is to write a more
-  coherent documentation.
-
-* **Implement merging rules.** Some details are still awaiting
-  discovery by me.
-
-* **Employ `unionmount` in eth-multiplexer.** I still have to scrounge
-  for details.
-
-* **Decide as to location of unionmount.** Presently, `unionmount` is
-  a (local) branch in `unionfs` git repository. The first step of
-  publishing it is planned to be pushing it to the Savannah `unionfs`
-  repository. Some agree that there should also be a second step
-  consisting in splitting `unionmount` in a separate git repository,
-  since the destinations of `unionfs` and `unionmount` are *similar*,
-  and not identical.
-
-* **Use a different (better?) implementation idea.** It has been
-  pointed out several times that `unionmount` could be implemented not
-  by forking off `unionfs`, but by keeping the merging functionality
-  in a stand-alone module (which could then be used by `unionfs` as
-  well). Different implementation ideas with their own specific
-  advantages may also arise in the future.
+* **Write documentation for `unionfs`.** *(5 Jun)* `unionfs` is not
+  exactly well-documented at the moment, the only help being provided
+  by the comments in the sources. The goal is to write a more coherent
+  documentation.
+
+* **Implement merging rules.** *(1 Aug)* Some details are still
+  awaiting discovery by me.
+
+* **Employ `unionmount` in eth-multiplexer.** *(10 Aug)* I still have
+  to scrounge for details.
+
+* **Decide as to location of unionmount.** *(1 Aug)* Presently,
+  `unionmount` is a (local) branch in `unionfs` git repository. The
+  first step of publishing it is planned to be pushing it to the
+  Savannah `unionfs` repository. Some agree that there should also be
+  a second step consisting in splitting `unionmount` in a separate git
+  repository, since the destinations of `unionfs` and `unionmount` are
+  *similar*, and not identical.
+
+* **Use a different (better?) implementation idea.** *(17 Aug)* It has
+  been pointed out several times that `unionmount` could be
+  implemented not by forking off `unionfs`, but by keeping the merging
+  functionality in a stand-alone module (which could then be used by
+  `unionfs` as well). Different implementation ideas with their own
+  specific advantages may also arise in the future.
 
 ---