OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: use code-tags instead of pre-tags

Browse Source 
Similar to the previous commit, code-tags seems more appropriate than
pre-tags here. So let's change it.

Fixes: ca0c1e69ca "docs: update releasing process to use new scripts and gitlab"
Acked-by: Dylan Baker <dylan@pnwbakers.com>
Reviewed-by: Eric Engestrom <eric@engestrom.ch>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3431>
This commit is contained in:
Erik Faye-Lund
2020-01-16 17:49:34 +01:00
parent 36e0275275
commit 1de361e56b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/releasing.html
View File

@@ -520,7 +520,7 @@ So we do a quick 'touch test'
<p> <p>
The release notes are completely generated by the The release notes are completely generated by the
<pre>bin/gen_release_notes.py</pre> script. Simply run this script before <code>bin/gen_release_notes.py</code> script. Simply run this script before
bumping the version bumping the version
The only thing left to do is add the sha256 sums. The only thing left to do is add the sha256 sums.
@@ -576,7 +576,7 @@ Something like the following steps will do the trick:
git cherry-pick -x X.Y git cherry-pick -x X.Y
</pre> </pre>
<p>Then run the <pre>./bin/post_verison.py X.Y.Z</pre>, where X.Y.Z is the <p>Then run the <code>./bin/post_verison.py X.Y.Z</code>, where X.Y.Z is the
version you just made. This will updated docs/relnotes.html and version you just made. This will updated docs/relnotes.html and
docs/index.html. Remove docs/release-calendar.html. Then commit and push: docs/index.html. Remove docs/release-calendar.html. Then commit and push:
</p> </p>