Remove double negative, and include the repeat usage across versions of a patch series.
Signed-off-by: Philip Oakley <philipoak...@iee.org> --- Documentation/git-format-patch.txt | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt index 066dc8b..751009c 100644 --- a/Documentation/git-format-patch.txt +++ b/Documentation/git-format-patch.txt @@ -196,13 +196,10 @@ will want to ensure that threading is disabled for `git send-email`. after the three-dash line. + The expected use case of this is to write supporting explanation for -the commit that does not belong to the commit log message proper -when (or after) you create the commit, and include it in your patch -submission. But if you can plan ahead and write it down, there may -not be a good reason not to write it in your commit message, and if -you can't, you can always edit the output of format-patch before -sending it out, so the practical value of this option is somewhat -dubious, unless your workflow is broken. +the commit, that does not belong to the commit log message proper, +and include it with the patch submission. The notes can be maintained +between versions of the patch series. You can also edit the output of +format-patch before sending. --[no]-signature=<signature>:: Add a signature to each message produced. Per RFC 3676 the signature -- 1.7.11.msysgit.1 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html