Re: [PATCH 1/5] Documentation: describe the format of messages with inline patches
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:51:03
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: [PATCH 1/5] Documentation: describe the format of messages with inline patches · Drew Northup <hidden>
- 2016-06-15 · [PATCH 1/5] Documentation: describe the format of messages with inline patches · Jonathan Nieder <hidden>
Drew Northup [off-list ref] 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