Lines Matching refs:summary

172 SHA-1 ID of the commit. Please also include the oneline summary of
189 SHA-1 ID, and the one line summary.  For example:
608     Subject: [PATCH 001/123] subsystem: summary phrase
637 The "summary phrase" in the email's Subject should concisely
638 describe the patch which that email contains.  The "summary
639 phrase" should not be a filename.  Do not use the same "summary
643 Bear in mind that the "summary phrase" of your email becomes a
645 into the git changelog.  The "summary phrase" may later be used in
647 google for the "summary phrase" to read discussion regarding that
653 For these reasons, the "summary" must be no more than 70-75
656 succinct and descriptive, but that is what a well-written summary
659 The "summary phrase" may be prefixed by tags enclosed in square
660 brackets: "Subject: [PATCH tag] <summary phrase>".  The tags are not
661 considered part of the summary phrase, but describe how the patch
695 it.  As in the "summary phrase", it is important to be both succinct as