Lines Matching full:describe

45 Describe your changes
48 Describe your problem.  Whether your patch is a one-line bug fix or
54 Describe user-visible impact.  Straight up crashes and lockups are
56 problem was spotted during code review, describe the impact you think
66 include numbers that back them up.  But also describe non-obvious
69 different workloads.  Describe the expected downsides of your
72 Once the problem is established, describe what you are actually doing
73 about it in technical detail.  It's important to describe the change
94 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
623     be copied to the permanent changelog to describe this patch.
645 describe the patch which that email contains.  The ``summary
661 characters, and it must describe both what the patch changes, as well
668 not considered part of the summary phrase, but describe how the patch
725 example of such comments might be ``patch changelogs`` which describe