diff options
| author | Carl Worth <cworth@cworth.org> | 2013-12-12 23:07:26 -0800 |
|---|---|---|
| committer | Carl Worth <cworth@cworth.org> | 2013-12-12 23:10:53 -0800 |
| commit | d6c8365795c4fb1af83b79f26f782e0834f6bdfc (patch) | |
| tree | e5284dc8c324c284aad9dd5148f68da5b6cf5ec1 /docs | |
| parent | 16c2919972bb477e6c0fd025eca450259c6a78e2 (diff) | |
| download | mesa-d6c8365795c4fb1af83b79f26f782e0834f6bdfc.tar.gz | |
docs: Update note regarding nominating patches for the stable branch.
This brings the documentation up to date with the current practice of using
the CC syntax for patch nomination.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/devinfo.html | 21 |
1 files changed, 18 insertions, 3 deletions
diff --git a/docs/devinfo.html b/docs/devinfo.html index 38c052ae96..a9d8b4f7db 100644 --- a/docs/devinfo.html +++ b/docs/devinfo.html @@ -190,11 +190,26 @@ you should add an appropriate note to the commit message. Here are some examples of such a note: </p> <ul> - <li>NOTE: This is a candidate for the 9.0 branch.</li> - <li>NOTE: This is a candidate for the 8.0 and 9.0 branches.</li> - <li>NOTE: This is a candidate for the stable branches.</li> + <li>CC: <mesa-stable@lists.freedesktop.org></li> + <li>CC: "9.2 10.0" <mesa-stable@lists.freedesktop.org></li> + <li>CC: "10.0" <mesa-stable@lists.freedesktop.org></li> </ul> +Simply adding the CC to the mesa-stable list address is adequate to nominate +the commit for the most-recently-created stable branch. It is only necessary +to specify a specific branch name, (such as "9.2 10.0" or "10.0" in the +examples above), if you want to nominate the commit for an older stable +branch. And, as in these examples, you can nominate the commit for the older +branch in addition to the more recent branch, or nominate the commit +exclusively for the older branch. + +This "CC" syntax for patch nomination will cause patches to automatically be +copied to the mesa-stable@ mailing list when you use "git send-email" to send +patches to the mesa-dev@ mailing list. Also, if you realize that a commit +should be nominate for the stable branch after it has already been commited, +you can send a note directly to the mesa-stable@lists.freedesktop.org where +the Mesa stable-branch maintainers will receive it. Be sure to mention the +commit ID of the commit of interest (as it appears in the mesa master branch). <h2>Cherry-picking candidates for a stable branch</h2> |