From d78863e049d6a18e8a090608fb39b333b56a3cc5 Mon Sep 17 00:00:00 2001 From: James McClune Date: Tue, 15 Jan 2019 22:42:05 -0500 Subject: [PATCH] SubmittingPatches: added inline markup to important references Signed-off-by: James McClune --- SubmittingPatches.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SubmittingPatches.rst b/SubmittingPatches.rst index 8ee0d1879ca57..a13191d857243 100644 --- a/SubmittingPatches.rst +++ b/SubmittingPatches.rst @@ -152,7 +152,7 @@ have been included in the discussion -------------------------------------------------------------- If this patch fixes a problem reported by somebody else, consider adding a -Reported-by: tag to credit the reporter for their contribution. This tag should +``Reported-by:`` tag to credit the reporter for their contribution. This tag should not be added without the reporter's permission, especially if the problem was not reported in a public forum. That said, if we diligently credit our bug reporters, they will, hopefully, be inspired to help us again in the future. @@ -254,7 +254,7 @@ email list to ensure your submission is noticed. When addressing review comments, can should either add additional patches to your branch or (better yet) squash those changes into the relevant commits so that the sequence of changes is "clean" and gets things right the first time. -The 'git rebase -i' command is very helpful in this process. Once you have +The ``git rebase -i`` command is very helpful in this process. Once you have updated your local branch, you can simply force-push to the existing branch in your public repository that is referenced by the pull request with -- 2.39.5