Lines Matching refs:summary

168 SHA-1 ID of the commit. Please also include the oneline summary of
185 the SHA-1 ID, and the one line summary.  For example::
626     Subject: [PATCH 001/123] subsystem: summary phrase
655 The ``summary phrase`` in the email's Subject should concisely
656 describe the patch which that email contains.  The ``summary
657 phrase`` should not be a filename.  Do not use the same ``summary
661 Bear in mind that the ``summary phrase`` of your email becomes a
663 into the ``git`` changelog.  The ``summary phrase`` may later be used in
665 google for the ``summary phrase`` to read discussion regarding that
671 For these reasons, the ``summary`` must be no more than 70-75
674 succinct and descriptive, but that is what a well-written summary
677 The ``summary phrase`` may be prefixed by tags enclosed in square
678 brackets: "Subject: [PATCH <tag>...] <summary phrase>".  The tags are
679 not considered part of the summary phrase, but describe how the patch
713 it.  As in the ``summary phrase``, it is important to be both succinct as