Author: brane
Date: Wed Sep 17 23:44:51 2025
New Revision: 1928576
Log:
Get rid of nested divisions for heading levels.
Modified:
apr/site/trunk/docs/anonsvn.html
apr/site/trunk/docs/compiling_unix.html
apr/site/trunk/docs/compiling_win32.html
apr/site/trunk/docs/coverage/index.html
apr/site/trunk/docs/download.html
apr/site/trunk/docs/guidelines.html
apr/site/trunk/docs/index.html
apr/site/trunk/docs/mailing-lists.html
apr/site/trunk/docs/patches.html
apr/site/trunk/docs/projects.html
apr/site/trunk/docs/security_report.html
apr/site/trunk/docs/versioning.html
apr/site/trunk/xdocs/stylesheets/site.vsl
Modified: apr/site/trunk/docs/anonsvn.html
==============================================================================
--- apr/site/trunk/docs/anonsvn.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/anonsvn.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="svn">
- <h1>How To Use Anonymous Subversion</h1>
+ <h1 id="svn">How To Use Anonymous Subversion</h1>
<blockquote>
<p>Developers with commit access to the Apache source tree normally
use Subversion to keep their local copies of the source tree up to
@@ -116,9 +115,7 @@ from earlier versions):</p></dt>
<p>You can also <a href="https://svn.apache.org/viewvc/apr/">browse the
repository using ViewVC</a>.</p>
</blockquote>
-</div>
- <div class="h1" id="sitesvn">
- <h1>Maintaining the Site</h1>
+ <h1 id="sitesvn">Maintaining the Site</h1>
<blockquote>
<p>Developers can check out the site as follows:</p>
<blockquote>
@@ -127,9 +124,7 @@ repository using ViewVC</a>.</p>
<p>After generating HTML and committing, the site is updated
automatically via <code>rsync</code>.</p>
</blockquote>
-</div>
- <div class="h1" id="testsvn">
- <h1>Publishing Test Packages</h1>
+ <h1 id="testsvn">Publishing Test Packages</h1>
<blockquote>
<p>Developers can check out the test package directory as follows:</p>
<blockquote>
@@ -138,9 +133,7 @@ repository using ViewVC</a>.</p>
<p>After committing, the site is updated automatically
via <code>svnpubsub</code>.</p>
</blockquote>
-</div>
- <div class="h1" id="releasesvn">
- <h1>Publishing Releases</h1>
+ <h1 id="releasesvn">Publishing Releases</h1>
<blockquote>
<p>Developers can check out release directory as follows:</p>
<blockquote>
@@ -164,7 +157,6 @@ repository using ViewVC</a>.</p>
the old (replaced) release from apr-release.</li>
</ol>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/compiling_unix.html
==============================================================================
--- apr/site/trunk/docs/compiling_unix.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/compiling_unix.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="fromsource">
- <h1>Building from Source</h1>
+ <h1 id="fromsource">Building from Source</h1>
<blockquote>
<p>We've attempted to ensure that compiling apr, apr-iconv and
apr-util distribution tarballs requires nothing more than what
@@ -83,9 +82,7 @@ make install
to run <code>./buildconf</code> before running the commands listed above.
</p>
</blockquote>
-</div>
- <div class="h1" id="fromrpm">
- <h1>Building RPMs (Redhat / CentOS / Fedora)</h1>
+ <h1 id="fromrpm">Building RPMs (Redhat / CentOS / Fedora)</h1>
<blockquote>
<p>While APR is available as an RPM for most distributions, it can
sometimes be desirable to install and use the canonical version of
@@ -94,8 +91,7 @@ make install
<p>While the APR project does not currently create binary RPMs for
the various distributions out there, it is easy to build your own
binary RPMs from the canonical APR and APR-Util tarballs as follows.</p>
-<div class="h2" id="creatingsrpms">
- <h2>Creating Source RPMs</h2>
+<h2 id="creatingsrpms">Creating Source RPMs</h2>
<blockquote>
<p>The APR and APR-Util source tarballs can be converted into SRPMs
as follows:</p>
@@ -104,9 +100,7 @@ make install
rpmbuild -ts apr-util-1.4.x.tar.bz2
</pre>
</blockquote>
-</div>
-<div class="h2" id="buildingrpms">
- <h2>Building RPMs</h2>
+<h2 id="buildingrpms">Building RPMs</h2>
<blockquote>
<p>The APR RPM can be built directly from the APR source tarball using
the following command:</p>
@@ -173,9 +167,7 @@ make install
<dd>Crypto NSS driver, dependent on Mozilla NSS.</dd>
</dl>
</blockquote>
-</div>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/compiling_win32.html
==============================================================================
--- apr/site/trunk/docs/compiling_win32.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/compiling_win32.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,20 +66,16 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="overview">
- <h1>Overview</h1>
+ <h1 id="overview">Overview</h1>
<blockquote>
<p>APR can be built on Windows using a cmake-based build system or with Visual
Studio project files maintained by APR developers. The cmake-based build system
directly supports more versions of Visual Studio but currently has considerable
functional limitations.</p>
</blockquote>
-</div>
- <div class="h1" id="vstudio">
- <h1>Building APR with the Included Visual Studio Project Files</h1>
+ <h1 id="vstudio">Building APR with the Included Visual Studio Project Files</h1>
<blockquote>
-<div class="h2" id="requirements">
- <h2>Requirements</h2>
+<h2 id="requirements">Requirements</h2>
<blockquote>
<p>Compiling apr, apr-iconv and/or apr-util requires the following environment
to be properly installed:</p>
@@ -110,9 +106,7 @@ Workbench or Microsoft Development Envir
often to cite.
</p>
</blockquote>
-</div>
-<div class="h2" id="layout">
- <h2>Required Directory Layout</h2>
+<h2 id="layout">Required Directory Layout</h2>
<blockquote>
<p>For a supported build, you must have apr, apr-iconv, and apr-util
checked-out in parallel directories. For example:</p>
@@ -127,9 +121,7 @@ should be sufficient.</p>
<p>Currently, the directories <strong>must</strong> be called apr, apr-iconv,
and apr-util. No exceptions.</p>
</blockquote>
-</div>
-<div class="h2" id="workspace">
- <h2>Developer Studio Workspace/Microsoft Development Environment IDE Build</h2>
+<h2 id="workspace">Developer Studio Workspace/Microsoft Development Environment IDE Build</h2>
<blockquote>
<p>APR can be compiled using Visual C++'s graphical environment.
To simplify this process, a complete Visual Studio workspace,
@@ -163,9 +155,7 @@ and apr-util. No exceptions.</p>
specific PATH options (as far as we can tell).
</p>
</blockquote>
-</div>
-<div class="h2" id="commandline">
- <h2>Command-Line Build</h2>
+<h2 id="commandline">Command-Line Build</h2>
<blockquote>
<p>If you use the command line, you must configure it:</p>
<blockquote>
@@ -208,15 +198,11 @@ msdev aprutil.dsw /MAKE \
export all .mak files yourself from the project.
</p>
</blockquote>
-</div>
-<div class="h2" id="integrating">
- <h2>Integrating the Library</h2>
+<h2 id="integrating">Integrating the Library</h2>
<blockquote>
<p>We should tell ya'll 'bout this, no?</p>
</blockquote>
-</div>
-<div class="h2" id="components">
- <h2>Library Components</h2>
+<h2 id="components">Library Components</h2>
<blockquote>
<p>The apr-util/aprutil.dsw workspace builds the .dsp projects of the
Apache server listed with dependent projects preceeding their
@@ -241,9 +227,7 @@ msdev aprutil.dsw /MAKE \
and apr-util symbols from being tagged as __declspec(dllimport),
eliminating compiliation warnings and speeding up execution.</p>
</blockquote>
-</div>
-<div class="h2" id="convert5">
- <h2>Converting the Project for Visual C++ 5.0</h2>
+<h2 id="convert5">Converting the Project for Visual C++ 5.0</h2>
<blockquote>
<p>The .dsp project files are distributed in Visual C++ 6.0 format. Visual
C++ 5.0 (97) will recognize them. To quickly prepare the .dsp files in
@@ -258,11 +242,8 @@ below will be listed as it is converted.
revises project files, please convert them back with the the -6 option instead
of -5, which returns the project files to Visual Studio 6.0 format.</p>
</blockquote>
-</div>
</blockquote>
-</div>
- <div class="h1" id="cmake">
- <h1>Building APR with cmake</h1>
+ <h1 id="cmake">Building APR with cmake</h1>
<blockquote>
<p>The primary documentation for this build mechanism is in the
<code>README.cmake</code> files in the APR and APR-util projects. Refer to those
@@ -277,7 +258,6 @@ considerations are described in <code>RE
project files.</li>
</ul>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/coverage/index.html
==============================================================================
--- apr/site/trunk/docs/coverage/index.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/coverage/index.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="coverage">
- <h1>APR Test Coverage</h1>
+ <h1 id="coverage">APR Test Coverage</h1>
<blockquote>
<p>This should give us some idea of how well our tests actually stress our
code. To generate this data, do the following:</p>
@@ -86,7 +85,6 @@ make gcov
unified framework, so this is correct.</p>
<!--#include virtual="/coverage/coverage.part.html" -->
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/download.html
==============================================================================
--- apr/site/trunk/docs/download.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/download.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="Download">
- <h1>Downloading the Apache Portable Runtime</h1>
+ <h1 id="Download">Downloading the Apache Portable Runtime</h1>
<blockquote>
<p>Use the links below to download the Apache Portable Runtime from one of
our mirrors. You <strong>must</strong> <a href="#verify">verify the
@@ -77,8 +76,7 @@ our main distribution directory.</p>
distribution site and its mirrors. Older releases are available from
the <a href="https://archive.apache.org/dist/apr/">archive download
site.</a></p>
-<div class="h2" id="mirror">
- <h2>Mirror</h2>
+<h2 id="mirror">Mirror</h2>
<blockquote>
<p>[if-any logo]
<a href="[link]"><img align="right" src="[logo]" border="0" /></a>[end]
@@ -103,9 +101,7 @@ Other mirrors: <select name="Preferred">
<p>You may also consult the <a href="https://www.apache.org/dyn/closer.lua">complete
list of mirrors</a>.</p>
</blockquote>
-</div>
-<div class="h2" id="apr1">
- <h2>APR 1.7.6 is the best available version</h2>
+<h2 id="apr1">APR 1.7.6 is the best available version</h2>
<blockquote>
<p>APR is the base portability library.</p>
<ul>
@@ -132,9 +128,7 @@ list of mirrors</a>.</p>
</ul>
</blockquote>
-</div>
-<div class="h2" id="aprutil1">
- <h2>APR-util 1.6.3 is the best available version</h2>
+<h2 id="aprutil1">APR-util 1.6.3 is the best available version</h2>
<blockquote>
<p>APR-util provides a number of helpful abstractions on top of APR.</p>
<ul>
@@ -161,9 +155,7 @@ list of mirrors</a>.</p>
</ul>
</blockquote>
-</div>
-<div class="h2" id="apriconv1">
- <h2>APR iconv 1.2.2 is the best available version</h2>
+<h2 id="apriconv1">APR iconv 1.2.2 is the best available version</h2>
<blockquote>
<p>APR-iconv provides a portable iconv() implementation built on top of APR.
It is generally of interest only where no system provided iconv() is
@@ -194,9 +186,7 @@ list of mirrors</a>.</p>
</ul>
</blockquote>
-</div>
-<div class="h2" id="verify">
- <h2>Verify the integrity of the files</h2>
+<h2 id="verify">Verify the integrity of the files</h2>
<blockquote>
<p>It is essential that you verify the integrity of the downloaded
files using the PGP signatures, using a tool such as GnuPG (GPG).
@@ -206,9 +196,7 @@ APR as to HTTP Server).</p>
<p>PGP public keys for individual Apache developers can be downloaded
(and fingerprints verified) at <a href="https://people.apache.org/keys/committer/">https://people.apache.org/keys/committer/</a>.</p>
</blockquote>
-</div>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/guidelines.html
==============================================================================
--- apr/site/trunk/docs/guidelines.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/guidelines.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,15 +66,12 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="projectguidelines">
- <h1>APR Project Guidelines</h1>
+ <h1 id="projectguidelines">APR Project Guidelines</h1>
<blockquote>
<p>This page describes the procedures and guidelines used by the APR
Project.</p>
</blockquote>
-</div>
- <div class="h1" id="commitaccess">
- <h1>Commit Access</h1>
+ <h1 id="commitaccess">Commit Access</h1>
<blockquote>
<p>Commit access will be somewhere between the "lengthy" process of httpd,
and the more "open" process in Subversion.</p>
@@ -86,9 +83,7 @@ from problematic committers (since we us
reserves the right to suspend commit privileges, if other APR members end up
spending too much time dealing with problematic commits.</p>
</blockquote>
-</div>
- <div class="h1" id="changeprocess">
- <h1>Change Process</h1>
+ <h1 id="changeprocess">Change Process</h1>
<blockquote>
<p>Most changes (bug fixes and minor, commonsense feature adds) do not
require review. Developers are encouraged to request review for:</p>
@@ -105,9 +100,7 @@ revert the change until it is approved.<
this time, the group does not see a need to ever use a "Review
Then Commit" (RTC) process.</p>
</blockquote>
-</div>
- <div class="h1" id="changesentries">
- <h1>CHANGES Entries</h1>
+ <h1 id="changesentries">CHANGES Entries</h1>
<blockquote>
<p>The goals for CHANGES entries are to provide this documentation
for user-visible changes and to limit this documentation to releases
@@ -120,9 +113,7 @@ from both branches.</p>
time, should be accompanied by a CHANGES entry in trunk (if a CHANGES
entry is appropriate at all).</p>
</blockquote>
-</div>
- <div class="h1" id="branchmaintenance">
- <h1>Branch Maintenance</h1>
+ <h1 id="branchmaintenance">Branch Maintenance</h1>
<blockquote>
<p>Many changes which are committed to trunk are also delivered to other
branches. The procedure used is outlined below.</p>
@@ -146,9 +137,7 @@ it was part of the trunk revision being
commonly omitted from the trunk commit if a backport will be performed
almost immediately.)</p>
</blockquote>
-</div>
- <div class="h1" id="pmcmembership">
- <h1>PMC Membership</h1>
+ <h1 id="pmcmembership">PMC Membership</h1>
<blockquote>
<p>PMC membership is attained through a "consensus approval" process
according to the <a href="http://httpd.apache.org/dev/guidelines.html">standard ASF guidelines</a> (as set out by HTTP Server). The voters are the
@@ -156,9 +145,7 @@ existing PMC members.</p>
<p>The general policy is to accept committers who have demonstrated
longevity in dev/doc/admin ability and interest in the APR project.</p>
</blockquote>
-</div>
- <div class="h1" id="decisionmaking">
- <h1>Decision Making: Consensus and Voting</h1>
+ <h1 id="decisionmaking">Decision Making: Consensus and Voting</h1>
<blockquote>
<p class="note">
<strong>Note</strong>:
@@ -206,25 +193,20 @@ not it has been reached.</p>
if such a change does reach the voting stage, then positive votes must
outnumber negative votes by a two-to-one ratio, or greater, for the change to
take effect.</p>
-<div class="h2" id="vetoes">
- <h2>Veto as a vote</h2>
+<h2 id="vetoes">Veto as a vote</h2>
<blockquote>
<p>A voter explicitly stating that they veto the decision, providing a
justification of their veto is sufficient to table a vote until the issue is
addressed and the vetoer or those who agreed concur that the the issue is
addressed.</p>
</blockquote>
-</div>
-<div class="h2" id="votingprocedures">
- <h2>Voting Procedure Technicalities</h2>
+<h2 id="votingprocedures">Voting Procedure Technicalities</h2>
<blockquote>
<p>Votes are tallied in the <code>STATUS</code> file, adjacent to the action
item under vote. All votes must be either sent to the mailing list or added
directly to the <code>STATUS</code> file entry for that action item.</p>
</blockquote>
-</div>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/index.html
==============================================================================
--- apr/site/trunk/docs/index.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/index.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="Welcome">
- <h1>Welcome</h1>
+ <h1 id="Welcome">Welcome</h1>
<blockquote>
<p>The mission of the Apache Portable Runtime (APR) project is to create and
maintain software libraries that provide a predictable and consistent interface
@@ -78,9 +77,7 @@ their software is built, relieving them
conditions to work around or take advantage of platform-specific deficiencies
or features.</p>
</blockquote>
-</div>
- <div class="h1" id="recommended">
- <h1>Recommended Releases</h1>
+ <h1 id="recommended">Recommended Releases</h1>
<blockquote>
<p>The recommended releases of the several Apache Portable Runtime
libraries are</p>
@@ -90,9 +87,7 @@ libraries are</p>
<li>APR-iconv 1.2.2, released October 22, 2017</li>
</ul>
</blockquote>
-</div>
- <div class="h1" id="apr17">
- <h1>Apache Portable Runtime 1.7.6 Released</h1>
+ <h1 id="apr17">Apache Portable Runtime 1.7.6 Released</h1>
<blockquote>
<p>
The Apache Software Foundation and the Apache Portable Runtime
@@ -113,9 +108,7 @@ Programmer's Manual:
<a href="docs/apr/1.7/">APR</a>
</p>
</blockquote>
-</div>
- <div class="h1" id="apu16">
- <h1>Apache Portable Runtime Utility 1.6.3 Released</h1>
+ <h1 id="apu16">Apache Portable Runtime Utility 1.6.3 Released</h1>
<blockquote>
<p>
The Apache Software Foundation and the Apache Portable Runtime
@@ -139,9 +132,7 @@ Programmer's Manual:
<a href="docs/apr-util/1.6/">APR-util</a>
</p>
</blockquote>
-</div>
- <div class="h1" id="Projects">
- <h1>Projects Using APR</h1>
+ <h1 id="Projects">Projects Using APR</h1>
<blockquote>
<p>After several years of development, APR is beginning to see use outside of
the Apache HTTP Server. To encourage more people to investigate APR for their
@@ -150,9 +141,7 @@ are currently using APR. If you are usi
recognized, please send e-mail to <a href="mailto:[email protected]"> the
developer's mailing list.</a></p>
</blockquote>
-</div>
- <div class="h1" id="Subprojects">
- <h1>APR Subprojects</h1>
+ <h1 id="Subprojects">APR Subprojects</h1>
<blockquote>
<p>The following is a list of supported development projects under the APR
Project. All of the development happens on the indicated mailing lists. See
@@ -184,15 +173,12 @@ these discussions. Or, check the <a hre
<li>API Documentation: <a href="docs/apr-iconv/trunk/">apr-iconv docs</a> (current stable branch)</li>
</ul>
</blockquote>
-</div>
- <div class="h1" id="Start">
- <h1>How To Start Developing with APR</h1>
+ <h1 id="Start">How To Start Developing with APR</h1>
<blockquote>
<p>We hope this website starts you in the right direction. Please read the
docs and tutorials for the project you are interested in. If you have
suggestions of any sort, please feel free to send us an email at <a href="mailto:[email protected]">[email protected]</a>!</p>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/mailing-lists.html
==============================================================================
--- apr/site/trunk/docs/mailing-lists.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/mailing-lists.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="mailinglists">
- <h1>APR Mailing Lists</h1>
+ <h1 id="mailinglists">APR Mailing Lists</h1>
<blockquote>
<p>The APR Project makes very heavy use of mailing lists. All of these are <a href="https://cr.yp.to/ezmlm.html">ezmlm</a> lists, which means that if you
want to subscribe to <b><em>list</em>@apr.apache.org</b> then you want to email
@@ -75,9 +74,7 @@ want to subscribe to <b><em>list</em>@ap
help with the various ezmlm commands for a given list, email
<b><em>list</em>[email protected]</b>. Details given below.</p>
</blockquote>
-</div>
- <div class="h1" id="apr-dev">
- <h1>Development Mailing List</h1>
+ <h1 id="apr-dev">Development Mailing List</h1>
<blockquote>
<p>
The <code><a href="mailto:[email protected]">[email protected]</a></code>
@@ -113,9 +110,7 @@ help with the various ezmlm commands for
</tr>
</table>
</blockquote>
-</div>
- <div class="h1" id="apr-bugs">
- <h1>Automated Bugs Notification Mailing List</h1>
+ <h1 id="apr-bugs">Automated Bugs Notification Mailing List</h1>
<blockquote>
<p>
This list is used to notify developers of changes to the bugzilla
@@ -149,9 +144,7 @@ help with the various ezmlm commands for
</tr>
</table>
</blockquote>
-</div>
- <div class="h1" id="apr-commits">
- <h1>Automated Commit Notification Mailing List</h1>
+ <h1 id="apr-commits">Automated Commit Notification Mailing List</h1>
<blockquote>
<p>
This list is used to notify developers of changes to the master
@@ -186,7 +179,6 @@ help with the various ezmlm commands for
</tr>
</table>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/patches.html
==============================================================================
--- apr/site/trunk/docs/patches.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/patches.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="creatingpatches">
- <h1>Creating Patches</h1>
+ <h1 id="creatingpatches">Creating Patches</h1>
<blockquote>
<p>Like most Open Source projects, APR thrives on contributions from people
who use it in their own projects. We want to make it as easy as possible for
@@ -78,9 +77,7 @@ reviewed, but it will take longer and at
developers. When you contribute, please remember that anyone evaluating your
suggestion is a voulenteer contributor, just like yourself.</p>
</blockquote>
-</div>
- <div class="h1" id="codingstyle">
- <h1>Code Style</h1>
+ <h1 id="codingstyle">Code Style</h1>
<blockquote>
<p>Currently APR is using the same code format as Apache. The Apache
style-guide was debated for a long time before it the Apache Group settled on
@@ -103,9 +100,7 @@ to produce a segfault when it attempts t
increases the stability of consumer code, by forcing developers to fix code
which might otherwise silently ignores fatal error conditions.</p>
</blockquote>
-</div>
- <div class="h1" id="patchformat">
- <h1>Patch Format</h1>
+ <h1 id="patchformat">Patch Format</h1>
<blockquote>
<p>We request that patches be submitted in unified diff format:</p>
<blockquote><code>diff -u file-old.c file.c</code></blockquote>
@@ -131,9 +126,7 @@ context is crucial to understanding your
goes. Patches without filenames, line numbers and surrounding context become
impossible to consider as time goes on.</p>
</blockquote>
-</div>
- <div class="h1" id="submitting">
- <h1>Submitting Your Patch</h1>
+ <h1 id="submitting">Submitting Your Patch</h1>
<blockquote>
<p>The best place to submit your patch is an attachment to a bug report:</p>
<blockquote><code><a href="https://issues.apache.org/bugzilla/">https://issues.apache.org/bugzilla/</a></code></blockquote>
@@ -164,7 +157,6 @@ your stuff is important as well.</p>
freeze", when they are trying to iron out the remaining bugs in the code in
preparation for a release.</p>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/projects.html
==============================================================================
--- apr/site/trunk/docs/projects.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/projects.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,15 +66,12 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="submit">
- <h1>Submit your project!</h1>
+ <h1 id="submit">Submit your project!</h1>
<blockquote>
<p>Do you use APR? Send an email to [email protected] with your project
name and a URL to get added to this list!</p>
</blockquote>
-</div>
- <div class="h1" id="open_source">
- <h1>Open Source Projects Using APR</h1>
+ <h1 id="open_source">Open Source Projects Using APR</h1>
<blockquote>
<p>The following open source projects are known to use APR:</p>
<ul>
@@ -90,7 +87,6 @@ name and a URL to get added to this list
<li><a href="https://redwax.eu/rt/">Redwax Tool</a></li>
</ul>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/security_report.html
==============================================================================
--- apr/site/trunk/docs/security_report.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/security_report.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="reporting">
- <h1>Reporting New Security Problems with APR</h1>
+ <h1 id="reporting">Reporting New Security Problems with APR</h1>
<blockquote>
<p>The Apache Software Foundation takes a very active stance in eliminating
security problems and denial of service attacks against the
@@ -89,7 +88,6 @@ the same URL repeatedly). In general ou
attacks which can cause the server to consume resources in a non-linear
relationship to the size of inputs.</p>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/docs/versioning.html
==============================================================================
--- apr/site/trunk/docs/versioning.html Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/docs/versioning.html Wed Sep 17 23:44:51 2025 (r1928576)
@@ -66,8 +66,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="numbering">
- <h1>APR's Version Numbering</h1>
+ <h1 id="numbering">APR's Version Numbering</h1>
<blockquote>
<p>This document covers how the APR projects are versioned. Since the APR
projects are libraries, it is very important to define a stable API for users
@@ -87,9 +86,7 @@ next.</p>
<li><a href="#notes">Other Notes</a></li>
</ul>
</blockquote>
-</div>
- <div class="h1" id="basics">
- <h1>The Basics</h1>
+ <h1 id="basics">The Basics</h1>
<blockquote>
<p> Versions are denoted using a standard triplet of integers:
<code><strong>MAJOR.MINOR.PATCH</strong></code>. The basic intent is that
@@ -103,9 +100,7 @@ backwards.</p>
Before a 1.0 release (version 0.x.y), the API <em>can</em> and <em>will</em> be
changing freely, without regard to the restrictions detailed below.</p>
</blockquote>
-</div>
- <div class="h1" id="source">
- <h1>Source Compatibility</h1>
+ <h1 id="source">Source Compatibility</h1>
<blockquote>
<p>We define "source compatible" to mean that an application will continue
to build without error, and that the semantics will remain unchanged.</p>
@@ -115,9 +110,7 @@ However, if an application uses an API w
particular minor version, it (obviously) will no longer build or operate
against previous minor versions.</p>
</blockquote>
-</div>
- <div class="h1" id="binary">
- <h1>Binary Compatibility</h1>
+ <h1 id="binary">Binary Compatibility</h1>
<blockquote>
<p> We define "binary compatible" to mean that a compiled application can
be linked (possibly dynamically) against the library and continue to function
@@ -127,9 +120,7 @@ against a particular version will contin
versions (unless the major number changes). It is possible that an application
will not be able to successfully link against a previous minor version.</p>
</blockquote>
-</div>
- <div class="h1" id="examples">
- <h1>Examples</h1>
+ <h1 id="examples">Examples</h1>
<blockquote>
<p>Here are some examples to demonstrate the compatibility:</p>
<table>
@@ -185,14 +176,11 @@ will not be able to successfully link ag
the versions may be compatible, depending very precisely upon the particular
APIs used by the application.</p>
</blockquote>
-</div>
- <div class="h1" id="strategy">
- <h1>Strategy</h1>
+ <h1 id="strategy">Strategy</h1>
<blockquote>
<p>This section details how we will build the code to meet the above
requirements and guidelines.</p>
-<div class="h2" id="patchversions">
- <h2>Patch Version</h2>
+<h2 id="patchversions">Patch Version</h2>
<blockquote>
<p>To retain perfect source and binary compatibility, a patch release can only
change function implementations. Changes to the API, to the signatures of
@@ -200,9 +188,7 @@ public functions, or to the interpretati
<strong>not allowed</strong>. Effectively, these releases are pure bug fix
releases.</p>
</blockquote>
-</div>
-<div class="h2" id="minorversions">
- <h2>Minor Versions</h2>
+<h2 id="minorversions">Minor Versions</h2>
<blockquote>
<p>Minor releases can introduce new functions, new symbolic and enumerated
constants, and deprecate existing functions.</p>
@@ -298,9 +284,7 @@ constants, and deprecate existing functi
</dd>
</dl>
</blockquote>
-</div>
-<div class="h2" id="majorversions">
- <h2>Major Versions</h2>
+<h2 id="majorversions">Major Versions</h2>
<blockquote>
<p>Any kind of change can be made during a major version release. Particular
types of changes that might occur:</p>
@@ -310,18 +294,14 @@ types of changes that might occur:</p>
<li>fold together macro-ized function replacements</li>
</ul>
</blockquote>
-</div>
</blockquote>
-</div>
- <div class="h1" id="vsncheck">
- <h1>Version Checking</h1>
+ <h1 id="vsncheck">Version Checking</h1>
<blockquote>
<p>In many cases, the user of a library will need to check the version that
they are compiling against, or that is being used at runtime. Because of the
strict rules of source and binary compatibility, these checks can be simpler
and more complicated depending on what is needed.</p>
-<div class="h2" id="compiletimechecks">
- <h2>Compile-Time Checks</h2>
+<h2 id="compiletimechecks">Compile-Time Checks</h2>
<blockquote>
<p>Libraries should make their version number available as compile-time
constants. For example:</p>
@@ -344,9 +324,7 @@ are (say) simply different choices of va
application can support a wider variety of installed libraries if it avoids
compile-time checks.</p>
</blockquote>
-</div>
-<div class="h2" id="runtimechecks">
- <h2>Run-Time Checks</h2>
+<h2 id="runtimechecks">Run-Time Checks</h2>
<blockquote>
<p>A library meeting this specification should support a way for an
application to determine the library's version at <em>run-time</em>. This will
@@ -369,11 +347,8 @@ that all applications will continue to f
in a minor release, then it is possible to use a compile-time check, but that
would create a tighter coupling to the library. </p>
</blockquote>
-</div>
</blockquote>
-</div>
- <div class="h1" id="parallel">
- <h1>Parallel Installation</h1>
+ <h1 id="parallel">Parallel Installation</h1>
<blockquote>
<p><em>Parallel installation</em> refers to the ability to install multiple
versions of a library simultaneously -- they exist in parallel. This document
@@ -382,8 +357,7 @@ detail how this versioning specification
to <a href="https://ometer.com/parallel.html">Havoc Pennington's
"Parallel Installation" essay</a> for futher details and the rationale behind this form of parallel
installation.</p>
-<div class="h2" id="librarynaming">
- <h2>Library Naming</h2>
+<h2 id="librarynaming">Library Naming</h2>
<blockquote>
<p>On Unix-ish platforms, the library name should include the <code>MAJOR</code>
version number: </p>
@@ -409,9 +383,7 @@ are relegated to the library name after
<p>The implication here is that build systems for libraries should arrange
to generate <code>.so</code> libraries matching the above pattern. </p>
</blockquote>
-</div>
-<div class="h2" id="includedirs">
- <h2>Include Directories</h2>
+<h2 id="includedirs">Include Directories</h2>
<blockquote>
<p>The default installation directory for a library's include files should
specify the <code>MAJOR</code> version number, and should normally be installed as
@@ -429,9 +401,7 @@ include path and include the files norma
<p>Depending upon the API that the application is designed to work against, it
can simply include different versions of the include directory.</p>
</blockquote>
-</div>
-<div class="h2" id="otherfiles">
- <h2>Other Files</h2>
+<h2 id="otherfiles">Other Files</h2>
<blockquote>
<p><strong>NOTE:</strong> There is no recommendation at this time for the
best and proper handling of, say, <code>FOO-config</code> types of files. Or
@@ -439,18 +409,14 @@ non-code types of files (e.g. things tha
like <code>/usr/shared</code>).</p>
<p>Further thought and exploration is needed here.</p>
</blockquote>
-</div>
</blockquote>
-</div>
- <div class="h1" id="notes">
- <h1>Other Notes</h1>
+ <h1 id="notes">Other Notes</h1>
<blockquote>
<p>It is expected that other libraries, besides those in the APR project, will
want to use the above definitions of versioning. This is quite fine, and those
libraries can simply reference this document. Its canonical location is: </p>
<blockquote>https://apr.apache.org/versioning.html</blockquote>
</blockquote>
-</div>
</div>
</div>
Modified: apr/site/trunk/xdocs/stylesheets/site.vsl
==============================================================================
--- apr/site/trunk/xdocs/stylesheets/site.vsl Wed Sep 17 23:29:42 2025 (r1928575)
+++ apr/site/trunk/xdocs/stylesheets/site.vsl Wed Sep 17 23:44:51 2025 (r1928576)
@@ -37,11 +37,9 @@
#set ($id = "")
#end
#if ($level == 1)
-<div class="h1" id="$id">
- <h1>$heading</h1>
+<h1 id="$id">$heading</h1>
#elseif ($level == 2)
-<div class="h2" id="$id">
- <h2>$heading</h2>
+<h2 id="$id">$heading</h2>
#end
<blockquote>
## Output the section-level children with transformers
@@ -60,11 +58,6 @@ $items
#end
#end
</blockquote>
-#if ($level == 1)
-</div>
-#elseif ($level == 2)
-</div>
-#end
#end
##
##
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.