aboutsummaryrefslogtreecommitdiff
path: root/doc/patchqueue
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-10-23 03:41:05 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-10-23 03:41:05 +0000
commit2a7082236e4a3ead43b2b58e79a810b5b69a0f63 (patch)
tree2bf96243bed72d22111946c4352be004629201cb /doc/patchqueue
parent01d894af98193881d300160e6cb70da17f36a38d (diff)
downloadikiwiki-2a7082236e4a3ead43b2b58e79a810b5b69a0f63.tar
ikiwiki-2a7082236e4a3ead43b2b58e79a810b5b69a0f63.tar.gz
web commit by EthanGlasserCamp: do I have to maintain this?
Diffstat (limited to 'doc/patchqueue')
-rw-r--r--doc/patchqueue/index.html_allowed/discussion.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/patchqueue/index.html_allowed/discussion.mdwn b/doc/patchqueue/index.html_allowed/discussion.mdwn
new file mode 100644
index 000000000..71c6e6f73
--- /dev/null
+++ b/doc/patchqueue/index.html_allowed/discussion.mdwn
@@ -0,0 +1,8 @@
+Any chance of this, or something like this, making it into the trunk?
+
+I realized that when writing Perl modules, having a Foo.pm, and then Foo/Bar.pm is the norm,
+so maybe that's why Ikiwiki does things this way. But I still think it's "more natural"
+in a web environment. (And Python, which is where I do my hacking, imports Foo/__init__.py
+if you import Foo.)
+
+Ethan \ No newline at end of file