You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
80 lines
2.1 KiB
80 lines
2.1 KiB
19 years ago
|
git-send-email(1)
|
||
|
=================
|
||
20 years ago
|
v0.1, July 2005
|
||
|
|
||
|
NAME
|
||
|
----
|
||
19 years ago
|
git-send-email - Send a collection of patches as emails
|
||
20 years ago
|
|
||
|
|
||
|
SYNOPSIS
|
||
|
--------
|
||
19 years ago
|
'git-send-email' [options] <file|directory> [... file|directory]
|
||
20 years ago
|
|
||
|
|
||
|
|
||
|
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.
|
||
|
|
||
19 years ago
|
--compose
|
||
|
Use \$EDITOR to edit an introductory message for the
|
||
|
patch series.
|
||
|
|
||
20 years ago
|
--subject
|
||
|
Specify the initial subject of the email thread.
|
||
19 years ago
|
Only necessary if --compose is also set. If --compose
|
||
|
is not set, this will be prompted for.
|
||
20 years ago
|
|
||
|
--in-reply-to
|
||
|
Specify the contents of the first In-Reply-To header.
|
||
|
Subsequent emails will refer to the previous email
|
||
19 years ago
|
instead of this if --chain-reply-to is set (the default)
|
||
|
Only necessary if --compose is also set. If --compose
|
||
|
is not set, this will be prompted for.
|
||
20 years ago
|
|
||
20 years ago
|
--chain-reply-to, --no-chain-reply-to
|
||
|
If this is set, each email will be sent as a reply to the previous
|
||
|
email sent. If disabled with "--no-chain-reply-to", all emails after
|
||
|
the first will be sent as replies to the first email sent. When using
|
||
|
this, it is recommended that the first file given be an overview of the
|
||
|
entire patch series.
|
||
|
Default is --chain-reply-to
|
||
|
|
||
|
--smtp-server
|
||
|
If set, specifies the outgoing SMTP server to use. Defaults to
|
||
|
localhost.
|
||
|
|
||
|
|
||
20 years ago
|
Author
|
||
|
------
|
||
|
Written by Ryan Anderson <ryan@michonline.com>
|
||
|
|
||
19 years ago
|
git-send-email is originally based upon
|
||
20 years ago
|
send_lots_of_email.pl by Greg Kroah-Hartman.
|
||
|
|
||
|
Documentation
|
||
|
--------------
|
||
|
Documentation by Ryan Anderson
|
||
|
|
||
|
GIT
|
||
|
---
|
||
|
Part of the link:git.html[git] suite
|
||
|
|