Re: cvs commit: httpd-2.0/docs/manual/vhosts fd-limits.xml.ja fd-limits.html.ja.jis

* Erik Abele wrote: > I know, and I also don't like to change the japanese files, but since > the file is really short I reviewed it 'visually': *big grin* nd -- die (eval q-qq:Just Another Perl Hacker :-) # André Malo, # ---

Re: cvs commit: httpd-2.0/docs/manual/vhosts fd-limits.xml.ja fd-limits.html.ja.jis

André Malo wrote: * [EMAIL PROTECTED] wrote: --- fd-limits.html.ja.jis 7 Nov 2002 07:07:04 - 1.4 +++ fd-limits.html.ja.jis 8 Nov 2002 21:35:07 - 1.5 hmm. there are too much differences for the one fixed typo. I can't read Japanese, what did change here additionall

Re: cvs commit: httpd-2.0/docs/manual/vhosts fd-limits.xml.ja fd-limits.html.ja.jis

* [EMAIL PROTECTED] wrote: > --- fd-limits.html.ja.jis 7 Nov 2002 07:07:04 - 1.4 > +++ fd-limits.html.ja.jis 8 Nov 2002 21:35:07 - 1.5 hmm. there are too much differences for the one fixed typo. I can't read Japanese, what did change here additionally? If you're in d

Re: broken links at http://httpd.apache.org/docs-2.0/mpm.html

* Joshua Slive wrote: > Please don't just remove the tags around those. Yes! should we introduce a new attribute "createanchor" (="no" in that case; "yes" would be default) or something? > The fact that > those links are broken is pointing out the more important fact that those > mpms have no

Re: broken links at http://httpd.apache.org/docs-2.0/mpm.html

Please don't just remove the tags around those. The fact that those links are broken is pointing out the more important fact that those mpms have no documentation. I'm perfectly happy seeing those links remain broken until the correct docs appear. On Fri, 8 Nov 2002, Rodent of Unusual Size wro

Re: broken links at http://httpd.apache.org/docs-2.0/mpm.html

not acked..--- Begin Message --- Hello, at the end of this page, in the "MPM Defaults" chapter there are four links: BeOS beos OS/2 mpmt_os2 Unix prefork Windows mpm_winnt Only "Unix" and "Windows" work. "Beos" and "OS/2" give 404 Not Found. --alexm --- End Message ---

Docs Example; The aftermath of an APACHE_2_0 branch

For those interested (expecially committers), this is how I picture cvs usage changing; I'm going to take the 'simple example' where we presume most docs efforts are committed back to the 2.0 branch from our development tree. And we will presume most folks work on docs within the 2.1-dev tree (th

RE: Final counting approaches...

At 07:49 AM 11/8/2002, Sander wrote: >I wouldn't mind taking on the RM job for 2.0.44. And I won't mind giving it away :-) However, prepare to lay down the tag Monday and start working with both the dev and docs lists to gather as much of the docs work into 2.0.44 as we can (under a 2_0_44_PRE1

Fwd: Final counting approaches...

Sorry, this should have been copied to the docs list as well from the get-go. The general idea of beginning the apache 2.0/2.1 split is to FIRST minimize any initial fixup, other than assure that the new auth docs remain in cvs HEAD (becoming 2.1) while we pick up 'just the right version' for auth