From c166afb676e0941f8deca6a788ce1cb4ae5e911c Mon Sep 17 00:00:00 2001 From: Travis Cross Date: Thu, 18 Sep 2014 21:08:14 +0000 Subject: [PATCH] Use preformatted text for example commit message We want to highlight that lines are hard wrapped in a commit message, and using the typical Markdown blockquote syntax fails to achieve that. --- docs/SubmittingPatches | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/SubmittingPatches b/docs/SubmittingPatches index 1cbcc08d95..e648530e0b 100644 --- a/docs/SubmittingPatches +++ b/docs/SubmittingPatches @@ -102,19 +102,19 @@ The commit subject is the first line of your commit message, then there is an empty line, then your commit body starts. A good commit message might look like this: -> Add frobinator support to mod_sofia -> -> Without proper frobinator support users had to make multiple calls -> to shell scripts to do the sort of frobbing needed in high call -> volume environments. -> -> With this change, we now link to libfrob and support the IETF -> draft-cross-voip-frobbing API. -> -> After appropriate amounts of frobbing have been done, a new variable -> `frobbing_done` is set in the caller's channel. -> -> FS-XXXX #resolve + Add frobinator support to mod_sofia + + Without proper frobinator support users had to make multiple calls + to shell scripts to do the sort of frobbing needed in high call + volume environments. + + With this change, we now link to libfrob and support the IETF + draft-cross-voip-frobbing API. + + After appropriate amounts of frobbing have been done, a new variable + `frobbing_done` is set in the caller's channel. + + FS-XXXX #resolve Patches Related to JIRA Issues ------------------------------