Lines Matching refs:describe

21 Many of these steps describe the default behavior of the git version
117 problem was spotted during code review, describe the impact you think
127 include numbers that back them up.  But also describe non-obvious
133 Once the problem is established, describe what you are actually doing
134 about it in technical detail.  It's important to describe the change
620     be copied to the permanent changelog to describe this patch.
640 describe the patch which that email contains.  The "summary
656 characters, and it must describe both what the patch changes, as well
663 not considered part of the summary phrase, but describe how the patch
709 which describe what has changed between the v1 and v2 version of the
777 changelog-style message to the tag; this is an ideal place to describe the