https://bz.apache.org/bugzilla/show_bug.cgi?id=70033
Philippe Cloutier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #7 from Philippe Cloutier <[email protected]> --- (In reply to Rich Bowen from comment #5) > All of the stuff in /ssl, /rewrite and /howto are designated "howtos" or > "tutorials", while the stuff in /mod are considered reference manuals. I don't see any such designation. 2 of these pages *are* indeed howto material, but the collection is designated as a "guide", and most of it is indeed a topical guide, with 1 reference page and these howto pages. > So perhaps you can see why I remain confused as to what pages exactly you > are talking about. But I *think* you're talking about content in the > /rewrite directory. Yes? I am not sure what explains the confusion, no. The page with the basic problem is indicated in the URL field. But the other pages are indeed in that directory. To be perfectly clear: * “The Summary in the mod_rewrite reference” is at https://httpd.apache.org/docs/trunk/en/mod/mod_rewrite.html. * The “Guide to Apache mod_rewrite” page, which I also referred to as “that index page”, is at https://httpd.apache.org/docs/trunk/en/rewrite/. * The “Apache mod_rewrite Introduction” page is at https://httpd.apache.org/docs/trunk/en/rewrite/intro.html. > However, I will read all of this carefully and try to figure out what > passages on which pages you're talking about. Thanks, but I don't mind clarifying which pages my reports refer to if that can be clearer. However, if I may, I *was* disappointed when I read you “remain[ed] unclear what change [I was] suggesting here.” It took me many minutes of reflection to guess what could be unclear in my suggestions, and all of the effort I made appears to have been wrong in the end. The huge effort you keep doing on documentation―in particular on rewriting―is highly appreciated, and I know you solved multiple issues before I even reported them, but it still took multiple person-days to report and follow up to all these tickets. I know the antiquated ITS engine is not helping, but I can assure you I take a lot of care to make my reports as clear as possible, and would appreciate some hints on how to improve if I fail. (In reply to Rich Bowen from comment #6) > Ok, over coffee this morning, and rereading your various tickets, I think I > have finally understood what you're going for. > > I've committed r1934081 which is an updated index file and a TODO of other > changes that seem useful. > > The goal is to treat /readme as one cohesive "document" - a multi-chapter > book. I've started by analyzing the overlaps (there are a few) and seeing > how we can improve this with cross-references and updated diagrams. I am not sure what you mean by “/readme”, but thank you very much. One notable omission in the TODO is overlap between the “Apache HTTP Server Tutorial: .htaccess files” and “Per-directory Rewrites” (and probably others). A couple comments on the addition: > This guide supplements <a href="../mod/mod_rewrite.html">the reference > manual</a> with annotated examples, conceptual explanations, and practical > advice. 1. I would not call mod_rewrite.html "the reference manual". My understanding is that the reference manual consists of all reference pages. The sitemap calls it “mod_rewrite reference documentation”. 2. “This guide supplements” suggests the reference page should be read before the guide, while in reality, at least the introduction should be read before the reference. > Meanwhile, I believe this specific ticket is addressed, albeit perhaps not > in the way that you intended. I discussed a couple of related issues in this ticket. Your change fully addresses the duplication I highlighted. However, the original/core issue is how the reference qualifies the guide, and that issue remains. The label still implies that the reference is not part of mod_rewrite documentation, or that it is less detailed than the guide, which is not the case. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
