summaryrefslogtreecommitdiff
path: root/community/weblogs/ArneBab
diff options
context:
space:
mode:
Diffstat (limited to 'community/weblogs/ArneBab')
-rw-r--r--community/weblogs/ArneBab/how-i-write-a-qoth.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn
index c98f3354..74dab6a9 100644
--- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn
+++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn
@@ -27,7 +27,7 @@ Now I identify 2 to 4 main news items by some kind of “helps the Hurd most whe
Finally I sort all the news items by intuition, crude logic I develop on-the-fly writing and the goal of making the qoth read somewhat like nice prose.
-On the way to that I commit every little to medium step. I never know when I have to abort due to an interruption (I’m sure tschwinge loves my super-non-atomic horrible-to-review commits - but better that than losing work == time, and I try to prefix the commit-messages with “news:” so he knows that it’s useless to review them as in-flight-patches…).
+On the way to that I commit every little to medium step. I never know when I have to abort due to an interruption (I’m sure tschwinge loves my super-non-atomic horrible-to-review commits :-) - but better that than losing work == time, and I try to prefix the commit-messages with “news:” so he knows that it’s useless to review them as in-flight-patches…).
Having finished the text (usually after 3 to 6 hours of overall work), I send it by mail to bug-hurd: <http://lists.gnu.org/archive/html/bug-hurd/>