summaryrefslogtreecommitdiff
path: root/lib/rob
diff options
context:
space:
mode:
authorstanley lieber <stanley.lieber@gmail.com>2015-09-26 19:10:40 -0400
committerstanley lieber <stanley.lieber@gmail.com>2015-09-26 19:10:40 -0400
commit4c841d0b46720390df695dab404e6c82cdd25ef6 (patch)
treeb30e4e0e134c3c343b9e2d2544ea14500ba54a44 /lib/rob
parentf9244d433ac557dd9982c4cfcfe3fca759efeb25 (diff)
downloadplan9front-4c841d0b46720390df695dab404e6c82cdd25ef6.tar.xz
fortunes: Please be respectful in this forum.
Diffstat (limited to 'lib/rob')
-rw-r--r--lib/rob5
1 files changed, 5 insertions, 0 deletions
diff --git a/lib/rob b/lib/rob
index ac1376ff8..ea7191f06 100644
--- a/lib/rob
+++ b/lib/rob
@@ -317,3 +317,8 @@ Please be respectful in this forum.
It sounds reasonable and should be easy enough to implement.
There is a widespread assumption that garbage collection and kernels cannot coexist but history shows a number of examples that demonstrate otherwise.
Speaking as a one-time kernel writer, I would have loved to have garbage collection available inside the kernel. Hell, half the code in the kernel is tied to memory management.
+Thanks for the report.
+It takes precautions but there are no guarantees.
+What is the problem you are trying to solve?
+Please be civil.
+I think this would be a mistake.