I'll be a bad boy and top-post on this reply, as well as add dev@ to the
list of recipients.
In docs@, we have been discussing the possibility of adding comments to
the various pages in our documentation. As the discussion has
progressed, we have settled on the idea of trying out Disqus as a
On May 4, 2012, at 9:58 AM, Daniel Gruno wrote:
[+/-1] Add commentary system to the trunk documentation.
Obviously, I'm +1 on this, as one of the folks who's been gently pushing for it
for years. This is something that the PHP docs do right. Integrating comments
into the documentation is a
+1
[+/-1] Add commentary system to the trunk documentation.
[+1] Add commentary system to the trunk documentation.
On Friday 04 May 2012, Daniel Gruno wrote:
[+/-1] Add commentary system to the trunk documentation.
+1
[+1] Add commentary system to the trunk documentation.
This may be worth a separate thread, but I'll just ask
it here, before I forget about it:
Any chance we'll see a backport of this to /current/ ?
If so, will we display the same comments as in /trunk/ ?
So long,
i
--
Igor Galić
Tel:
On 5/4/2012 8:58 AM, Daniel Gruno wrote:
[+/-1] Add commentary system to the trunk documentation.
+1
--
Daniel Ruggeri
Hi,
there are some parts of httpd where unit tests would allow easier
testing or more complete test coverage than tests written for the perl
framework. Examples include the ap_pcfg_* functions, the varbuf API,
the regex plus API, and new interfaces that are not yet used by any
module.
On 5/3/2012 5:57 PM, Chris Darroch wrote:
I promise I won't
be offended if anyone says it's a stupid hack and should never be
committed, because, well, it is arguably a very stupid hack.
Actually, I think one could make the argument that all of the headers
set by mod_proxy should be just as
[+/-1] Add commentary system to the trunk documentation.
+1
On 2012 5 4 15:04, Igor Galić i.ga...@brainsware.org wrote:
[+1] Add commentary system to the trunk documentation.
This may be worth a separate thread, but I'll just ask
it here, before I forget about it:
Any chance we'll see a backport of this to /current/ ?
If so, will we display the
Daniel Gruno wrote:
[+/-1] Add commentary system to the trunk documentation.
+1
Chris.
--
GPG Key ID: 088335A9
GPG Key Fingerprint: 86CD 3297 7493 75BC F820 6715 F54F E648 0883 35A9
12 matches
Mail list logo