committer's guide: document MFC to: and MFC with:
There are a couple of different forms of these in use. Add "MFC to:" and "MFC with:" tags consistent with the existing "MFC after:", and provide a description so that consistent values can be used. There are ongoing discussions about "X-MFC-*" tags which still need to be resolved and documented here, or general guidance on X-MFC-*. Reviewed by: bcr, ngie Differential Revision: https://reviews.freebsd.org/D10585
This commit is contained in:
parent
ee0ba4e85b
commit
57347080a0
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=50227
1 changed files with 15 additions and 0 deletions
|
@ -2585,6 +2585,21 @@ freebsd-mfc-after = 2 weeks</programlisting>
|
|||
<acronym>MFC</acronym> is planned.</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry><literal>MFC to:</literal></entry>
|
||||
<entry>If the commit should be merged to a subset of
|
||||
stable branches, specify the branch names.</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry><literal>MFC with:</literal></entry>
|
||||
<entry>If the commit should be merged together with
|
||||
a previous one in a single
|
||||
<acronym>MFC</acronym> commit (for example, where
|
||||
this commit corrects a bug in the previous change),
|
||||
specify the corresponding revision number.</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry><literal>Relnotes:</literal></entry>
|
||||
<entry>If the change is a candidate for inclusion in
|
||||
|
|
Loading…
Reference in a new issue