From: Stephen Boyd <bebarino@gmail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc tweak for git-send-email
Date: Wed, 10 Jun 2009 17:57:50 -0700 [thread overview]
Message-ID: <4A30568E.7060503@gmail.com> (raw)
In-Reply-To: <1244656571-15560-1-git-send-email-bonzini@gnu.org>
Paolo Bonzini wrote:
> 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.
> +
You are right that the docs don't mention this feature very clearly, but
this patch doesn't fill the hole for me.
How do I tell send-email to generate patches with format-patch? I know
from looking at the code that send-email actually calls format-patch
with the rev-list passed on the command line.
Maybe it would be more clear to say that rev-list can be specified in
the same way as format-patch? Also, could you update the first sentence
in the description section? Obviously send-email takes more than just
patches on the command line.
next prev parent reply other threads:[~2009-06-11 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 17:56 [PATCH] doc tweak for git-send-email Paolo Bonzini
2009-06-11 0:57 ` Stephen Boyd [this message]
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=4A30568E.7060503@gmail.com \
--to=bebarino@gmail.com \
--cc=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).