Lines Matching refs:change
10 - Inserts a cover letter with change lists
46 normally in the top commit so it is easy to change them with 'git
51 patches. Weeks later, change the patches and repeat, knowing that you
103 If you want to change the defaults for patman's command-line arguments,
267 particular version n of that commit. The change list is
269 change list and also the whole thing is repeated in the cover
270 letter (where duplicate change lines are merged).
272 By adding your change lists into your commits it is easier to
300 This tells patman to sort and/or uniq the change logs. Changes may be
301 multiple lines long, as long as each subsequent line of a change begins
304 - This change
306 - But this change is separate
309 unique entries. If omitted, no change log processing is done.
446 <change 'pick' to 'edit' in 89234f5>
537 Finally, you need to add a change log to the two commits you changed. You
538 add change logs to each individual commit where the changes happened, like
547 When you run patman it will collect all the change logs from the different
566 1. When you change back to the us-cmd branch days or weeks later all your
569 to, or anything about the change logs.
575 compare change and see what you did, you can either create a new branch for
588 6. It is a good idea to add the change log info as you change the commit,
590 go back and change or remove logs from commits.
599 change. For clarity, if there are no changes for this patch in the most
605 - Some change
608 - Another change
615 - Another change
618 - Some change