From: Paolo Bonzini <bonzini@gnu.org>
To: git@vger.kernel.org
Subject: [PATCH] doc tweak for git-send-email
Date: Wed, 10 Jun 2009 13:56:11 -0400 [thread overview]
Message-ID: <1244656571-15560-1-git-send-email-bonzini@gnu.org> (raw)
The git-send-email docs do not mention except in the usage lines
the combined patch formatting/sending ability of git-send-email.
This fills the hole.
Signed-off-by: Paolo Bonzini <bonzini@gnu.org>
---
Documentation/git-send-email.txt | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index eb851b3..02bb0d3 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -33,6 +33,9 @@ script
This format expects the first line of the file to contain the "Cc:" value
and the "Subject:" of the message as the second line.
+In addition, git send-email can be asked to generate patches with git
+format-patch and send them.
+
OPTIONS
-------
--
1.6.0.3
next reply other threads:[~2009-06-10 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 17:56 Paolo Bonzini [this message]
2009-06-11 0:57 ` [PATCH] doc tweak for git-send-email Stephen Boyd
2009-06-11 7:30 ` [PATCH v2] " Paolo Bonzini
2009-06-11 21:57 ` Stephen Boyd
2009-06-12 6:20 ` 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=1244656571-15560-1-git-send-email-bonzini@gnu.org \
--to=bonzini@gnu.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).