Lines Matching full:in

20 in accordance with the clauses specified in the
29   (a) The contribution was created in whole or in part by me and I
31       indicated in the file; or
36       work with modifications, whether created in whole or in part
39       in the file; or
53 be known by in the community, but should not be anonymous, nor misrepresent
56 It is generally expected that the name and email addresses used in one of the
59 address, but using multiple addresses in one commit just confuses
69 It is not uncommon for a patch to have contributions from multiple authors. In
71 line for each contributor involved in creation of the patch. Some edge cases:
74     considered not subject to copyright. In this case the secondary authors
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
94 in order of authorship, from oldest to newest.
117    behaviour of the patch in some manner, they should send an email reply
134 When a subsystem maintainer accepts a patch from a contributor, in addition to
138 At the time they queue the patch in their subsystem tree, the maintainer
140 done the aforementioned validation. This is in addition to any of their own
144 should record their contribution.  This is typically done via a note in the
156 for patches, avoiding the need for contributors to manually type in this
166 be used to append a suitable line in the emails it creates, without modifying
174 In the file ``$HOME/.emacs.d/abbrev_defs`` add:
192 In the file ``$HOME/.vimrc`` add::
216    ``Signed-off-by`` in the patch in addition to the orignal author's
218    done via a note in the commit message, just prior to the new contributor's
225 In complicated cases, or if otherwise unsure, ask for advice on the project
229 know you are interested in taking over their work, in case they still intended
235 Files in patches contributed to QEMU are generally expected to be provided
236 only in the preferred format for making modifications. The implication of
248    changes in the rasterization process / tools may affect quality. The
256    from a canonical list of build dependencies maintained in tree, together
258    included in tree because it is desirable to be able to directly build
265    sufficiently broadly available in distros.
267 In all cases above, the existence of generated files must be acknowledged
268 and justified in the commit that introduces them.
278 this should be declared in the commit message.
281 boilerplate code template which is then filled in to produce the final patch.
285 and licensing for their output. Note in particular the caveats applying to AI
297 The increasing prevalence of AI-assisted software development results in a
303 are made in accordance with the rules of the `Developer's Certificate of
327 included in contributions.
334 clarifed. In the meanwhile, requests for exceptions to this policy will be
337 copyright status for the tool's output in relation to its training model and