From: Junio C Hamano Date: Fri, 15 Apr 2011 20:24:38 GMT Subject: Re: [PATCH 1/5] Documentation: describe the format of messages with inline patches Message-ID: <7vbp07clfd.fsf@alter.siamese.dyndns.org> In-Reply-To: <1302898291.5926.9.camel@drew-northup.unet.maine.edu> Drew Northup writes: > Maybe I'm too picky, but I'd feel more comfortable saying: > > ... > dashes, and then sent as a message which in our example stars with > "arch/arm config files were..." On the receiving end, readers can save > ... Surely you are ;-) I am tempted to squash the following into it. Thanks. Documentation/git-format-patch.txt | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt index c20e0ed..eebfa5c 100644 --- a/Documentation/git-format-patch.txt +++ b/Documentation/git-format-patch.txt @@ -255,9 +255,9 @@ Do the same for ia64 so we can have sleek & trim looking Typically it will be placed in a MUA's drafts folder, edited to add timely commentary that should not go in the changelog after the three -dashes, and then sent as a message whose body starts with "arch/arm -config files were". On the receiving end, readers can save -interesting patches in a UNIX mailbox and apply them with +dashes, and then sent as a message whose body, in our example, starts +with "arch/arm config files were...". On the receiving end, readers +can save interesting patches in a UNIX mailbox and apply them with linkgit:git-am[1]. When a patch is part of an ongoing discussion, the patch generated by