Lines Matching full:by
14 Certification is achieved with a low overhead by adding a single line to the
17 Signed-off-by: YOUR NAME <YOUR@EMAIL>
27 By making a contribution to this project, I certify that:
29 (a) The contribution was created in whole or in part by me and I
37 by me, under the same open source license (unless I am
41 (c) The contribution was provided directly to me by some other
51 The name used with "Signed-off-by" does not need to be your legal name, nor
53 be known by in the community, but should not be anonymous, nor misrepresent
57 ``Signed-off-by`` lines, matches that of the git commit ``Author`` field.
63 nonetheless expected to add their own ``Signed-off-by`` to comply with the
70 this scenario, git commits will usually be expected to have a ``Signed-off-by``
75 need not include a ``Signed-off-by``.
79 their own ``Signed-off-by`` added unless their code suggestion was
80 unusually large, but it is common to add ``Suggested-by`` as a credit
86 It can be said that in this case a ``Signed-off-by`` is indicating that
89 ``Signed-off-by`` for each contributor, as in some countries employees are
93 When multiple ``Signed-off-by`` tags are present, they should be strictly kept
99 While the ``Signed-off-by`` tag is mandatory, there are a number of other tags
102 * **``Reviewed-by``**: when a QEMU community member reviews a patch on the
104 email reply containing a ``Reviewed-by`` tag. Subsystem maintainers who
106 ``Signed-off-by`` to the same commit.
108 * **``Acked-by``**: when a QEMU subsystem maintainer approves a patch that
111 ``Acked-by`` tag. Where a patch touches multiple subsystems, ``Acked-by``
114 a ``Reviewed-by`` tag.
116 * **``Tested-by``**: when a QEMU community member has functionally tested the
118 containing a ``Tested-by`` tag.
120 * **``Reported-by``**: when a QEMU community member reports a problem via the
122 it is good practice to credit them by including a ``Reported-by`` tag on
127 * **``Suggested-by``**: when a reviewer or other 3rd party makes non-trivial
129 by including a ``Suggested-by`` tag.
136 suitable ``Signed-off-by`` tags.
139 **must** also then add their own ``Signed-off-by`` to indicate that they have
141 ``Reviewed-by`` tags the subsystem maintainer may wish to include.
145 commit message, just prior to the maintainer's ``Signed-off-by``::
147 Signed-off-by: Cory Contributor <cory.contributor@example.com>
149 Signed-off-by: Mary Maintainer <mary.maintainer@mycorp.test>
152 Tools for adding ``Signed-off-by``
155 There are a variety of ways tools can support adding ``Signed-off-by`` tags
180 ("8rev" "Reviewed-by: YOUR NAME <your@email.addr>" nil 1)
181 ("8ack" "Acked-by: YOUR NAME <your@email.addr>" nil 1)
182 ("8test" "Tested-by: YOUR NAME <your@email.addr>" nil 1)
183 ("8sob" "Signed-off-by: YOUR NAME <your@email.addr>" nil 1)
186 with this change, if you type (for example) ``8rev`` followed by ``<space>``
194 iabbrev 8rev Reviewed-by: YOUR NAME <your@email.addr>
195 iabbrev 8ack Acked-by: YOUR NAME <your@email.addr>
196 iabbrev 8test Tested-by: YOUR NAME <your@email.addr>
197 iabbrev 8sob Signed-off-by: YOUR NAME <your@email.addr>
199 with this change, if you type (for example) ``8rev`` followed by ``<space>``
211 * Continue to credit the original author for their work, by maintaining their
212 original ``Signed-off-by``
215 * Acknowledge the extra work of the new contributor by including their
216 ``Signed-off-by`` in the patch in addition to the orignal author's
219 ``Signed-off-by``::
221 Signed-off-by: Some Person <some.person@example.com>
223 Signed-off-by: New Person <new.person@mycorp.test>
241 generated code is permitted, provided it is also accompanied by the
271 manipulation, driven by user specified inputs, are not generally considered
299 QEMU. Of particular concern is content generated by `Large Language Models
329 Examples of tools impacted by this policy includes GitHub's CoPilot, OpenAI's
335 evaluated by the QEMU project on a case by case basis. To be granted an