diff options
| author | Erik Faye-Lund <[email protected]> | 2019-04-18 15:38:01 +0200 |
|---|---|---|
| committer | Erik Faye-Lund <[email protected]> | 2019-05-02 11:09:15 +0000 |
| commit | 92917e82e866155dd1d9300186e3be97cd673b47 (patch) | |
| tree | fbf497e9311c52a0668af87639d184192ae258bf /docs/submittingpatches.html | |
| parent | 0c3bab776162b451f34ff14e015c56560ca9f9db (diff) | |
docs: close paragraphs before lists
paragraphs can't contain lists, and attempting to close them after
the list just cause an extra, empty paragraph to be created. We don't
want that, so let's close the paragraphs before the list intead.
Signed-off-by: Erik Faye-Lund <[email protected]>
Reviewed-by: Eric Engestrom <[email protected]>
Diffstat (limited to 'docs/submittingpatches.html')
| -rw-r--r-- | docs/submittingpatches.html | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index 957fdcd5cdc..6b9a07357b3 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -228,14 +228,14 @@ your email administrator for this.) </p> <p> Add labels to your MR to help reviewers find it. For example: - <ul> - <li>Mesa changes affecting all drivers: mesa - <li>Hardware vendor specific code: amd, intel, nvidia, ... - <li>Driver specific code: anvil, freedreno, i965, iris, radeonsi, - radv, vc4, ... - <li>Other tag examples: gallium, util - </ul> </p> +<ul> + <li>Mesa changes affecting all drivers: mesa + <li>Hardware vendor specific code: amd, intel, nvidia, ... + <li>Driver specific code: anvil, freedreno, i965, iris, radeonsi, + radv, vc4, ... + <li>Other tag examples: gallium, util +</ul> <p> Tick the following when creating the MR. It allows developers to rebase your work on top of master. @@ -255,18 +255,18 @@ your email administrator for this.) </p> <p> Some other notes: - <ul> - <li>Make changes and update your branch based on feedback - <li>Old, stale MR may be closed, but you can reopen it if you - still want to pursue the changes - <li>You should periodically check to see if your MR needs to be - rebased - <li>Make sure your MR is closed if your patches get pushed outside - of GitLab - <li>Please send MRs from a personal fork rather than from the main - Mesa repository, as it clutters it unnecessarily. - </ul> </p> +<ul> + <li>Make changes and update your branch based on feedback + <li>Old, stale MR may be closed, but you can reopen it if you + still want to pursue the changes + <li>You should periodically check to see if your MR needs to be + rebased + <li>Make sure your MR is closed if your patches get pushed outside + of GitLab + <li>Please send MRs from a personal fork rather than from the main + Mesa repository, as it clutters it unnecessarily. +</ul> <h2 id="reviewing">Reviewing Patches</h2> |