Thread (2 messages) flat view 2 messages, 2 authors, 2016-06-15

Re: [PATCH 2/5] Documentation: explain how to check for patch corruption

From: Jonathan Nieder <hidden>
Date: 2016-06-15 22:51:02

Junio C Hamano wrote:
Jonathan Nieder [off-list ref] writes:
quoted
+++ b/Documentation/SubmittingPatches
[...]
quoted
+While you are at it, check the resulting commit log message from
+a trial run of applying the patch.  If what is in the resulting
[...]
Perhaps the last paragraph can also go, as a copy of it now is in git-am(1)?
Yes, good idea.  I wanted to keep a reminder to look over the
resulting commit (and especially its log message), but this section is
definitely not the place.
quoted
+++ b/Documentation/git-format-patch.txt
@@ -286,6 +286,52 @@ title is likely to be different from the subject
+One way to test if your MUA is set up correctly is:
+
+* Send the patch to yourself, exactly the way you would, except
+  with To: and Cc: lines that do not contain the list and
+  maintainer address.
... "except for removing other people from To: and Cc: lines to avoid
spamming them with your test"?
Yes, that is much clearer.  If you'd like, I can collect other
corrections and read it over again myself to resend tomorrow.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help