Lines Matching full:describe

41 Describe your changes
44 Describe your problem.  Whether your patch is a one-line bug fix or
50 Describe user-visible impact.  Straight up crashes and lockups are
52 problem was spotted during code review, describe the impact you think
62 include numbers that back them up.  But also describe non-obvious
65 different workloads.  Describe the expected downsides of your
68 Once the problem is established, describe what you are actually doing
69 about it in technical detail.  It's important to describe the change
90 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
588     be copied to the permanent changelog to describe this patch.
610 describe the patch which that email contains.  The ``summary
626 characters, and it must describe both what the patch changes, as well
633 not considered part of the summary phrase, but describe how the patch
690 example of such comments might be ``patch changelogs`` which describe