From: Junio C Hamano <gitster@pobox•com>
To: Drew Northup <drew.northup@maine•edu>
Cc: Jonathan Nieder <jrnieder@gmail•com>,
Jim Meyering <jim@meyering•net>, git list <git@vger•kernel.org>,
Yann Dirson <ydirson@altern•org>,
Stephen Boyd <bebarino@gmail•com>
Subject: Re: [PATCH 1/5] Documentation: describe the format of messages with inline patches
Date: Fri, 15 Apr 2011 13:24:38 -0700 [thread overview]
Message-ID: <7vbp07clfd.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1302898291.5926.9.camel@drew-northup.unet.maine.edu> (Drew Northup's message of "Fri, 15 Apr 2011 16:11:31 -0400")
Drew Northup <drew.northup@maine•edu> 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
next prev parent reply other threads:[~2011-04-15 20:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 15:39 [PATCH] remove doubled words, e.g., s/to to/to/, and fix related typos Jim Meyering
2011-04-13 18:35 ` Drew Northup
2011-04-13 21:22 ` Jim Meyering
2011-04-13 22:17 ` [PATCH/RFC] Documentation/format-patch: summarize patch-sending workflow Jonathan Nieder
2011-04-13 22:38 ` Junio C Hamano
2011-04-14 21:11 ` [PATCH v2] Documentation: summarize how format-patch output is consumed Jonathan Nieder
2011-04-14 22:05 ` Junio C Hamano
2011-04-15 2:11 ` [PATCH/RFC v3 0/5] Documentation/format-patch: more hints on submitting patches Jonathan Nieder
2011-04-15 2:22 ` [PATCH 1/5] Documentation: describe the format of messages with inline patches Jonathan Nieder
2011-04-15 20:11 ` Drew Northup
2011-04-15 20:24 ` Junio C Hamano [this message]
2011-04-15 2:24 ` [PATCH 2/5] Documentation: explain how to check for patch corruption Jonathan Nieder
2011-04-15 4:53 ` Junio C Hamano
2011-04-15 6:17 ` Jonathan Nieder
2011-04-15 2:28 ` [PATCH 3/5] Documentation: hints for sending patches inline with Thunderbird Jonathan Nieder
2011-04-15 2:32 ` [PATCH 4/5] Documentation: publicize KMail hints for sending patches inline Jonathan Nieder
2011-04-17 13:57 ` Michele Ballabio
2011-04-15 2:33 ` [PATCH 5/5] Documentation: publicize hints for sending patches with GMail Jonathan Nieder
2011-04-15 7:41 ` [PATCH/RFC 6/5] Documentation/format-patch: suggest Toggle Word Wrap add-on for Thunderbird Johannes Sixt
2011-04-15 17:54 ` Junio C Hamano
2011-04-15 18:01 ` Michael J Gruber
2011-04-15 18:49 ` Junio C Hamano
2011-04-15 20:17 ` Jonathan Nieder
2011-04-18 6:31 ` [PATCH 6/5 v2] " Johannes Sixt
2011-04-13 22:26 ` [PATCH] remove doubled words, e.g., s/to to/to/, and fix related typos Jakub Narebski
2011-04-13 18:47 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vbp07clfd.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=bebarino@gmail$(echo .)com \
--cc=drew.northup@maine$(echo .)edu \
--cc=git@vger$(echo .)kernel.org \
--cc=jim@meyering$(echo .)net \
--cc=jrnieder@gmail$(echo .)com \
--cc=ydirson@altern$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox