Lines Matching full:describe

40 Describe your changes
43 Describe your problem.  Whether your patch is a one-line bug fix or
49 Describe user-visible impact.  Straight up crashes and lockups are
51 problem was spotted during code review, describe the impact you think
61 include numbers that back them up.  But also describe non-obvious
64 different workloads.  Describe the expected downsides of your
67 Once the problem is established, describe what you are actually doing
68 about it in technical detail.  It's important to describe the change
89 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
571     be copied to the permanent changelog to describe this patch.
593 describe the patch which that email contains.  The ``summary
609 characters, and it must describe both what the patch changes, as well
616 not considered part of the summary phrase, but describe how the patch
662 which describe what has changed between the v1 and v2 version of the