Lines Matching refs:change
10 - Inserts a cover letter with change lists
41 normally in the top commit so it is easy to change them with 'git
46 patches. Weeks later, change the patches and repeat, knowing that you
98 If you want to change the defaults for patman's command-line arguments,
240 particular version n of that commit. The change list is
242 change list and also the whole thing is repeated in the cover
243 letter (where duplicate change lines are merged).
245 By adding your change lists into your commits it is easier to
256 This tells patman to sort and/or uniq the change logs. It is
257 assumed that each change log entry is only a single line long.
259 unique entries. If omitted, no change log processing is done.
343 <change 'pick' to 'edit' in 89234f5>
418 Finally, you need to add a change log to the two commits you changed. You
419 add change logs to each individual commit where the changes happened, like
428 When you run patman it will collect all the change logs from the different
445 1. When you change back to the us-cmd branch days or weeks later all your
448 to, or anything about the change logs.
454 compare change and see what you did, you can either create a new branch for
467 6. It is a good idea to add the change log info as you change the commit,
469 go back and change or remove logs from commits.