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.  Do not split the tag across multiple
658     Subject: [PATCH 001/123] subsystem: summary phrase
687 The ``summary phrase`` in the email's Subject should concisely
688 describe the patch which that email contains.  The ``summary
689 phrase`` should not be a filename.  Do not use the same ``summary
693 Bear in mind that the ``summary phrase`` of your email becomes a
695 into the ``git`` changelog.  The ``summary phrase`` may later be used in
697 google for the ``summary phrase`` to read discussion regarding that
703 For these reasons, the ``summary`` must be no more than 70-75
706 succinct and descriptive, but that is what a well-written summary
709 The ``summary phrase`` may be prefixed by tags enclosed in square
710 brackets: "Subject: [PATCH <tag>...] <summary phrase>".  The tags are
711 not considered part of the summary phrase, but describe how the patch
745 it.  As in the ``summary phrase``, it is important to be both succinct as