Lines Matching +full:j +full:- +full:to +full:- +full:k

6 If you are a subsystem or branch maintainer, sometimes you need to slightly
7 modify patches you receive in order to merge them, because the code is not
8 exactly the same in your tree and the submitters'. If you stick strictly to
10 to rediff, but this is a totally counter-productive waste of time and energy.
11 Rule (b) allows you to adjust the code, but then it is very impolite to change
12 one submitters code and make him endorse your bugs. To solve this problem, it
13 is recommended that you add a line between the last Signed-off-by header and
16 name, all enclosed in square brackets, is noticeable enough to make it obvious
17 that you are responsible for last-minute changes. Example::
19        Signed-off-by: Random J Developer <random@developer.example.org>
20        [lucky@maintainer.example.org: struct foo moved from foo.c to foo.h]
21        Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
24 want at the same time to credit the author, track changes, merge the fix,
29 Special note to back-porters: It seems to be a common and useful practice
30 to insert an indication of the origin of a patch at the top of the commit
31 message (just after the subject line) to facilitate tracking. For instance,
32 here's what we see in a 3.x-stable release::
34   Date:   Tue Oct 7 07:26:38 2014 -0400
36     libata: Un-break ATA blacklist
48 Whatever the format, this information provides a valuable help to people
49 tracking your trees, and to people trying to troubleshoot bugs in your