Lines Matching refs:commit

43 normally in the top commit so it is easy to change them with 'git
44 commit --amend'
146 Similar to the above, but skip the first commit and take the next 5. This
147 is useful if your top commit is for setting up testing.
165 commit. Most can only appear once in the whole series.
209 	the commit messages, but do want to send, The notes are joined
218 	Similar, but for a single commit (patch). These notes will appear
232 	tag to the relevant commit and the script will include it when
240 	This can appear in any commit. It lists the changes for a
241 	particular version n of that commit. The change list is
242 	created based on this information. Each commit gets its own
247 	keep track of what happened. When you amend a commit, remember
283 in the subject are also picked up to Cc patches. For example, a commit like
287 commit 10212537b85ff9b6e09c82045127522c0f0db981
316 commit, and type 'patman' to check and send them.
354 the destination. So amend the top commit with:
356     git commit --amend
358 Use your editor to add some tags, so that the whole commit message is:
395 so you can drop your wip commit. So you resync with upstream:
401 the ack tag to one commit:
405 update the Series-cc: in the top commit:
410 series is now version two, so the series info in the top commit looks like
420 add change logs to each individual commit where the changes happened, like
468 6. It is a good idea to add the change log info as you change the commit,
489 putting an incorrect tag in a commit may provide a confusing message.