1Tags: No line splitting
2-----------------------
3Do not split a tag across multiple lines, tags are exempt from the
4"wrap at 75 columns" rule in order to simplify parsing scripts.  For
5example:
6
7        Fixes: 67d01cdb5518 ("x86: infrastructure to allow converting certain indirect calls to direct ones")
8
9
10Fixes Tag
11---------
12
13If your patch fixes a bug in a specific commit, e.g. you found an issue using
14``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
15the SHA-1 ID, and the one line summary.
16
17The following ``git config`` settings can be used to add a pretty format for
18outputting the above style in the ``git log`` or ``git show`` commands:
19
20        [core]
21                abbrev = 12
22        [pretty]
23                fixes = Fixes: %h (\"%s\")
24
25
26Backport Tag
27------------
28
29A backport tag is an optional tag in the commit message to request a
30given commit to be backported to the released trees:
31
32    Backport: 4.9+
33
34It marks a commit for being a candidate for backports to all released
35trees from 4.9 onward.
36
37The backport requester is expected to specify which currently supported
38releases need the backport; but encouraged to specify a release as far
39back as possible which applies. If the requester doesn't know the oldest
40affected tree, they are encouraged to append a comment like the
41following:
42
43    Backport: 4.9+ # maybe older
44
45Maintainers request the Backport tag to be added on commit. Contributors
46are welcome to mark their patches with the Backport tag when they deem
47appropriate. Maintainers will request for it to be removed when that is
48not the case.
49
50Please note that the Backport tag is a **request** for backport, which
51will still need to be evaluated by the maintainers. Maintainers might
52ask the requester to help with the backporting work if it is not
53trivial.
54
55When possible, please use the Fixes tag instead (or in addition).
56