Lines Matching full:change
12 - Inserts a cover letter with change lists
43 normally in the top commit so it is easy to change them with 'git
48 patches. Weeks later, change the patches and repeat, knowing that you
100 If you want to change the defaults for patman's command-line arguments,
241 particular version n of that commit. The change list is
243 change list and also the whole thing is repeated in the cover
244 letter (where duplicate change lines are merged).
246 By adding your change lists into your commits it is easier to
257 This tells patman to sort and/or uniq the change logs. It is
258 assumed that each change log entry is only a single line long.
260 unique entries. If omitted, no change log processing is done.
268 Change-Id:
344 <change 'pick' to 'edit' in 89234f5>
376 Change-Id: Ica71a14c1f0ecb5650f771a32fecb8d2eb9d8a17
419 Finally, you need to add a change log to the two commits you changed. You
420 add change logs to each individual commit where the changes happened, like
429 When you run patman it will collect all the change logs from the different
446 1. When you change back to the us-cmd branch days or weeks later all your
449 to, or anything about the change logs.
455 compare change and see what you did, you can either create a new branch for
468 6. It is a good idea to add the change log info as you change the commit,
470 go back and change or remove logs from commits.