Lines Matching refs:by

53 If you must generate your patches by hand, use "diff -up" or "diff -uprN"
54 to create patches.  Git generates patches in this form by default; if
58 generated by diff(1).  When creating your patch, make sure to create it
59 in "unified diff" format, as supplied by the '-u' argument to diff(1).
87 "dontdiff" is a list of files which are generated by the kernel during
97 #3.  This will facilitate review by other kernel developers,
160 If the patch fixes a logged bug entry, refer to that bug entry by
216 change that can be verified by reviewers.  Each patch should be justifiable
298 toward the stable maintainers by putting a line like this:
328  Non-portable code replaced by portable code (even in arch-specific,
330  Any fix by the author/maintainer of the file (ie. patch monkey
343 For this reason, all patches should be submitted by e-mail "inline".
426         (a) The contribution was created in whole or in part by me and I
434             by me, under the same open source license (unless I am
438         (c) The contribution was provided directly to me by some other
450 	Signed-off-by: Random J Developer <random@developer.example.org>
465 you add a line between the last Signed-off-by header and yours, indicating
471 	Signed-off-by: Random J Developer <random@developer.example.org>
473 	Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
505 12) When to use Acked-by: and Cc:
508 The Signed-off-by: tag indicates that the signer was involved in the
513 ask to have an Acked-by: line added to the patch's changelog.
515 Acked-by: is often used by the maintainer of the affected code when that
518 Acked-by: is not as formal as Signed-off-by:.  It is a record that the acker
521 into an Acked-by: (but note that it is usually better to ask for an
524 Acked-by: does not necessarily indicate acknowledgement of the entire patch.
525 For example, if a patch affects multiple subsystems and has an Acked-by: from
533 This is the only tag which might be added without an explicit action by the
539 13) Using Reported-by:, Tested-by:, Reviewed-by:, Suggested-by: and Fixes:
542 The Reported-by tag gives credit to people who find bugs and report them and it
545 Reported-by tag.
547 A Tested-by: tag indicates that the patch has been successfully tested (in
548 some environment) by the person named.  This tag informs maintainers that
552 Reviewed-by:, instead, indicates that the patch has been reviewed and found
557 	By offering my Reviewed-by: tag, I state that:
577 A Reviewed-by tag is a statement of opinion that the patch is an
580 offer a Reviewed-by tag for a patch.  This tag serves to give credit to
582 done on the patch.  Reviewed-by: tags, when supplied by reviewers known to
586 A Suggested-by: tag indicates that the patch idea is suggested by the person
597 method for indicating a bug fixed by the patch. See #2 above for more details.
622   - The "Signed-off-by:" lines, described above, which will
632 alphabetically by subject line - pretty much any email reader will
661 The "summary phrase" may be prefixed by tags enclosed in square
716 generates appropriate diffstats by default.)
769 signed by one or more core kernel developers.  This step can be hard for