From 5c20249242f8847f8b52882ccc49d6eb2611704d Mon Sep 17 00:00:00 2001
From: Mathieu Arnold <mat@FreeBSD.org>
Date: Tue, 10 Jul 2018 08:38:43 +0000
Subject: Add a tip about how to ask for a MFH when using a blanket approval.

Sponsored by:	Absolight
---
 en_US.ISO8859-1/articles/committers-guide/article.xml | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

(limited to 'en_US.ISO8859-1/articles/committers-guide')

diff --git a/en_US.ISO8859-1/articles/committers-guide/article.xml b/en_US.ISO8859-1/articles/committers-guide/article.xml
index f84e5ab709..1aaf2d2922 100644
--- a/en_US.ISO8859-1/articles/committers-guide/article.xml
+++ b/en_US.ISO8859-1/articles/committers-guide/article.xml
@@ -4375,6 +4375,20 @@ Relnotes:           yes</programlisting>
 	      to the &a.ports-secteam; and the &a.portmgr; with the
 	      revision number and a small description of why the
 	      commit needs to be merged.</para>
+
+	    <tip>
+	      <para>If the MFH is covered by a blanket approval,
+		please explain why with a couple of words on the
+		<literal>MFH</literal> line, so that the reviewing
+		team can skip this commit and save time.  For
+		example:</para>
+
+	      <programlisting>MFH:  <replaceable>2014Q1 (runtime fix)</replaceable>
+MFH:  <replaceable>2014Q1 (browser blanket)</replaceable></programlisting>
+
+	      <para>The list of blanket approvals is available in
+		<xref linkend="ports-qa-blanket"/>.</para>
+	    </tip>
 	  </answer>
 	</qandaentry>
 
-- 
cgit v1.2.3