diff options
| author | Emil Velikov <[email protected]> | 2018-11-07 16:02:58 +0000 |
|---|---|---|
| committer | Emil Velikov <[email protected]> | 2018-11-15 15:48:13 +0000 |
| commit | 4ae749acf1537d63585e056210a03f89466f61b2 (patch) | |
| tree | b48bcefe9a9901d8658b4d5866829214e63a26de | |
| parent | 19a081473f4f2a71c4888d27df247079ce1f5276 (diff) | |
docs/submittingpatches.html: correctly handle the <p> tag
As pointed out by the w3c validator.
Signed-off-by: Emil Velikov <[email protected]>
Reviewed-by: Juan A. Suarez <[email protected]>
| -rw-r--r-- | docs/submittingpatches.html | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index e5350bdb2cf..b84f01c3b37 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -156,9 +156,11 @@ As mentioned at the begining, patches should be bisectable. A good way to test this is to make use of the `git rebase` command, to run your tests on each commit. Assuming your branch is based off <code>origin/master</code>, you can run: +</p> <pre> $ git rebase --interactive --exec "make check" origin/master </pre> +<p> replacing <code>"make check"</code> with whatever other test you want to run. </p> |