git: a527f32556 - main - committers-guide: Bring back MFH metadata field

Mateusz Piotrowski <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
The branch main has been updated by 0mp:

URL: https://cgit.FreeBSD.org/doc/commit/?id=a527f3255652174c5a4ac7acdea672ed2a95b21c

commit a527f3255652174c5a4ac7acdea672ed2a95b21c
Author:     Mateusz Piotrowski <[email protected]>
AuthorDate: 2021-04-20 12:42:40 +0000
Commit:     Mateusz Piotrowski <[email protected]>
CommitDate: 2021-04-20 12:56:44 +0000

    committers-guide: Bring back MFH metadata field
    
    The MFH field is still useful to note that the commit is going to be
    merged into a quarterly branch.
    
    Reported by:    mat
    Reviewed by:    mat
    Differential Revision: https://reviews.freebsd.org/D29862
---
 documentation/content/en/articles/committers-guide/_index.adoc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index f0548fbce5..08968c1516 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -2584,6 +2584,9 @@ Approved by: re (username)
 |`MFC with:`
 |If the commit should be merged together with a previous one in a single MFC commit (for example, where this commit corrects a bug in the previous change), specify the corresponding Git hash.
 
+|`MFH:`
+|If the commit is to be merged into a ports quarterly branch name, specify the quarterly branch. For example `2021Q2`.
+
 |`Relnotes:`
 |If the change is a candidate for inclusion in the release notes for the next release from the branch, set to `yes`.
 
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/dev-commits-doc-all
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.