summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--Documentation/releases/checklist.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/releases/checklist.md b/Documentation/releases/checklist.md
index 1cfb1100c8..d777f0e38b 100644
--- a/Documentation/releases/checklist.md
+++ b/Documentation/releases/checklist.md
@@ -198,16 +198,16 @@ the coreboot server, and put them in the release directory at
````
People can now see the release tarballs on the website at
-https://www.coreboot.org/releases/
+<https://www.coreboot.org/releases/>
-The downloads page is the official place to download the releases from, and it needs to be updated with links to the new release tarballs and .sig files. It can be found at https://review.coreboot.org/cgit/homepage.git/tree/downloads.html
+The downloads page is the official place to download the releases from, and it needs to be updated with links to the new release tarballs and .sig files. It can be found at <https://review.coreboot.org/cgit/homepage.git/tree/downloads.html>
-Here is an example commit to change it: https://review.coreboot.org/#/c/19515/
+Here is an example commit to change it: <https://review.coreboot.org/c/homepage/+/19515>
## Upload crossgcc sources
Sometimes the source files for older revisions of
crossgcc disappear. To deal with that we maintain a mirror at
-https://www.coreboot.org/releases/crossgcc-sources/ where we host the
+<https://www.coreboot.org/releases/crossgcc-sources/> where we host the
sources used by the crossgcc scripts that are part of coreboot releases.
Run
@@ -221,7 +221,7 @@ sources. Download them yourself and copy them into the crossgcc-sources
directory on the server.
## After the release is complete
-Post the release notes on https://blogs.coreboot.org
+Post the release notes on <https://blogs.coreboot.org>
## Making a branch
At times we will need to create a branch, generally for patch fixes.