diff options
| author | Andreas Boll <andreas.boll.dev@gmail.com> | 2012-06-12 09:05:36 +0200 |
|---|---|---|
| committer | Brian Paul <brianp@vmware.com> | 2012-06-12 08:03:30 -0600 |
| commit | 210a27d8c33634c6b676a8a1d35d5fec98213181 (patch) | |
| tree | 572c8613bfcbc31b48f79b3cb6656f5bfc9fc5f9 /docs/devinfo.html | |
| parent | cc4188895be5525fa15c8b64b8338f901eda82fc (diff) | |
docs: prefer lowercase html tags
Signed-off-by: Brian Paul <brianp@vmware.com>
Diffstat (limited to 'docs/devinfo.html')
| -rw-r--r-- | docs/devinfo.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/devinfo.html b/docs/devinfo.html index 06322d1ce4d..c4b719469ce 100644 --- a/docs/devinfo.html +++ b/docs/devinfo.html @@ -53,7 +53,7 @@ To add a new GL extension to Mesa you have to do at least the following. -<H2>Coding Style</H2> +<h2>Coding Style</h2> <p> Mesa's code style has changed over the years. Here's the latest. @@ -149,20 +149,20 @@ src/mesa/state_tracker/st_glsl_to_tgsi.cpp can serve as examples. </p> -<H2>Making a New Mesa Release</H2> +<h2>Making a New Mesa Release</h2> <p> These are the instructions for making a new Mesa release. </p> -<H3>Get latest source files</H3> +<h3>Get latest source files</h3> <p> Use git to get the latest Mesa files from the git repository, from whatever branch is relevant. </p> -<H3>Verify and update version info</H3> +<h3>Verify and update version info</h3> <p> Create/edit the docs/relnotes-x.y.html file to document what's new in the release. Add the new relnotes-x.y.html file to <a href="relnotes.html">relnotes.html</a>. @@ -193,7 +193,7 @@ Then: <code>git push origin mesa_X_Y</code> </p> -<H3>Make the tarballs</H3> +<h3>Make the tarballs</h3> <p> Make the distribution files. From inside the Mesa directory: <pre> @@ -211,7 +211,7 @@ Copy the distribution files to a temporary directory, unpack them, compile everything, and run some demos to be sure everything works. </p> -<H3>Update the website and announce the release</H3> +<h3>Update the website and announce the release</h3> <p> Follow the directions on SourceForge for creating a new "release" and uploading the tarballs. |