From a40ebe73a1e0e3a4b7b5be464f1bd7952bd1c394 Mon Sep 17 00:00:00 2001
From: Emil Velikov <emil.veliko@collabora.com>
Date: Mon, 13 Feb 2017 19:23:41 +0000
Subject: [PATCH] docs/submittingpatches.html: document the Fixes tag
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

Provide information and an example.

Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
Reviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>
---
 docs/submittingpatches.html | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html
index 564ad731b24..6ca39c48259 100644
--- a/docs/submittingpatches.html
+++ b/docs/submittingpatches.html
@@ -78,6 +78,11 @@ patch comment.  For example:
 <pre>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89689
 </pre>
+<li>If a patch addresses a issue introduced with earlier commit, that should be
+noted in the patch comment.  For example:
+<pre>
+   Fixes: d7b3707c612 "util/disk_cache: use stat() to check if entry is a directory"
+</pre>
 <li>If there have been several revisions to a patch during the review
 process, they should be noted such as in this example:
 <pre>
-- 
2.30.2