From: Ryan Anderson <ryan@michonline.com>
To: junkio@cox.net, git@vger.kernel.org
Cc: ryan@michonline.com
Subject: [PATCH 2/3] Add documentation for git-send-email-script
Date: Sun, 31 Jul 2005 04:17:25 -0400 [thread overview]
Message-ID: <112279784541@foobar.com> (raw)
In-Reply-To: <11227978451100@foobar.com>
Signed-off-by: Ryan Anderson <ryan@michonline.com>
---
Documentation/git-send-email-script.txt | 61 +++++++++++++++++++++++++++++++
1 files changed, 61 insertions(+), 0 deletions(-)
create mode 100644 Documentation/git-send-email-script.txt
799a6320d3b07347869093beec303afbc005cf26
diff --git a/Documentation/git-send-email-script.txt b/Documentation/git-send-email-script.txt
new file mode 100644
--- /dev/null
+++ b/Documentation/git-send-email-script.txt
@@ -0,0 +1,61 @@
+git-send-email-script(1)
+=======================
+v0.1, July 2005
+
+NAME
+----
+git-send-email-script - Send a collection of patches as emails
+
+
+SYNOPSIS
+--------
+'git-send-email-script' [options] <file|directory> [... file|directory]
+
+
+
+DESCRIPTION
+-----------
+Takes the patches given on the command line and emails them out.
+
+The header of the email is configurable by command line options. If not
+specified on the command line, the user will be prompted with a ReadLine
+enabled interface to provide the necessary information.
+
+The options available are:
+
+ --to
+ Specify the primary recipient of the emails generated.
+ Generally, this will be the upstream maintainer of the
+ project involved.
+
+ --from
+ Specify the sender of the emails. This will default to
+ the value GIT_COMMITTER_IDENT, as returned by "git-var -l".
+ The user will still be prompted to confirm this entry.
+
+ --subject
+ Specify the initial subject of the email thread.
+
+ --in-reply-to
+ Specify the contents of the first In-Reply-To header.
+ Subsequent emails will refer to the previous email
+ instead of this.
+ When overriding on the command line, it may be necessary
+ to set this to a space. For example
+ --in-reply-to=" "
+
+Author
+------
+Written by Ryan Anderson <ryan@michonline.com>
+
+git-send-email-script is originally based upon
+send_lots_of_email.pl by Greg Kroah-Hartman.
+
+Documentation
+--------------
+Documentation by Ryan Anderson
+
+GIT
+---
+Part of the link:git.html[git] suite
+
next prev parent reply other threads:[~2005-07-31 8:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 8:17 [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31 8:17 ` Ryan Anderson [this message]
2005-07-31 8:17 ` [PATCH 3/3] Add new dependencies caused by git-send-email-script to debian/control Ryan Anderson
2005-07-31 8:24 ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31 9:36 ` Matthias Urlichs
2005-07-31 9:45 ` Junio C Hamano
2005-07-31 19:13 ` Junio C Hamano
2005-07-31 23:52 ` Ryan Anderson
2005-08-01 0:40 ` Junio C Hamano
2005-08-01 7:59 ` Matthias Urlichs
[not found] ` <20050801220800.GA12331@uglybox.localnet>
[not found] ` <20050801224308.GB12331@uglybox.localnet>
[not found] ` <7vk6j52qhn.fsf_-_@assigned-by-dhcp.cox.net>
2005-08-02 12:48 ` [OT] Perl-ish perl vs. C-ish perl Noel Maddy
2005-08-02 16:37 ` Junio C Hamano
2005-08-02 17:20 ` Noel Maddy
2005-08-03 1:30 ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-08-03 7:32 ` Matthias Urlichs
2005-07-31 10:25 ` Johannes Schindelin
2005-07-31 23:54 ` Ryan Anderson
2005-07-31 10:50 ` Sergey Vlasov
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=112279784541@foobar.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).