summaryrefslogtreecommitdiff
path: root/doc/patchqueue
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-02-18 23:27:38 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-02-18 23:27:38 +0000
commit75e0c2f66872131e8be8cb3778dbda9e48a1b719 (patch)
tree189a3543051a2337e7eb3e4ba742ed9d3d62db99 /doc/patchqueue
parent62126ad847c7e0395842e5f4acb8f1c48c260364 (diff)
web commit by http://id.inelegant.org/
Diffstat (limited to 'doc/patchqueue')
-rw-r--r--doc/patchqueue/lib-fixup.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/patchqueue/lib-fixup.mdwn b/doc/patchqueue/lib-fixup.mdwn
index 479f3a5a2..c8c145189 100644
--- a/doc/patchqueue/lib-fixup.mdwn
+++ b/doc/patchqueue/lib-fixup.mdwn
@@ -13,6 +13,9 @@ I imagine that there's a clean and elegant solution to this, but the hack I'm cu
> You could remove the taint switch locally, it's very unlikely to find
> tainting problems that nobody else has noticed. --[[Joey]]
+>> I completely understand rejecting this patch, but would you accept one to automate the removal of -T as a `make` option, then? I was trying to install Ikiwiki on a very popular
+>> web host, and the aforementioned issue took quite a while to debug; I imagine many people would have simply given up. -- Ben
+
<pre>
Index: Makefile.PL
===================================================================