Lines Matching refs:commit
46 normally in the top commit so it is easy to change them with 'git
47 commit --amend'
151 Similar to the above, but skip the first commit and take the next 5. This
152 is useful if your top commit is for setting up testing.
170 commit. Most can only appear once in the whole series.
235 the commit messages, but do want to send, The notes are joined
244 Similar, but for a single commit (patch). These notes will appear
258 tag to the relevant commit and the script will include it when
266 This can appear in any commit. It lists the changes for a
267 particular version n of that commit. The change list is
268 created based on this information. Each commit gets its own
273 keep track of what happened. When you amend a commit, remember
281 only appear in the changelog of the commit this tag is in. This is
338 in the subject are also picked up to Cc patches. For example, a commit like
342 commit 10212537b85ff9b6e09c82045127522c0f0db981
418 commit, and type 'patman' to check and send them.
456 the destination. So amend the top commit with:
458 git commit --amend
460 Use your editor to add some tags, so that the whole commit message is:
497 so you can drop your wip commit.
501 Add this to a tag in your top commit:
505 You can use then patman to collect the Acked-by tag to the correct commit,
522 Then update the Series-cc: in the top commit to add the person who reviewed
528 series is now version two, so the series info in the top commit looks like
538 add change logs to each individual commit where the changes happened, like
588 6. It is a good idea to add the change log info as you change the commit,
596 "Cover-letter" for maintainers to fetch the original commit.
601 with the following tags in the commit
634 putting an incorrect tag in a commit may provide a confusing message.