From 1c788676959a67f1da3e2fc4818ba6e02ec3f0ed Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Fri, 16 Aug 2013 03:30:41 +0200 Subject: sending patches MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- using-git.texinfo | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) (limited to 'using-git.texinfo') diff --git a/using-git.texinfo b/using-git.texinfo index c62bf0f..62e263b 100644 --- a/using-git.texinfo +++ b/using-git.texinfo @@ -529,6 +529,39 @@ being included, but is rather for discussion, use `PATCH/RFC'@footnote{RFC is an abbreviation for `Request for comments'} instead of `PATCH'. +To send the patch, use @command{git send-email}: + +@example +git send-email --to=EMAIL_ADDRESS_TO_SEND_TO PATCH_FILE +@end example + +If you have registered to the mailing list, +or for some other reason, want to send under +a different e-mail address then you made the +commits with, you need to specify an envelop +send, by adding an option: + +@example +--envelope-sender=SENDER_EMAIL_ADDRESS +@end example + +You will also need the specify which SMTP +server to use, authorisation and configurations: + +@example +--smtp-server=DOMAIN # it usally is prefixed with smtp. +--smtp-server-port=PORT +--smtp-encryption=ssl # or tls +--smtp-user=ACCOUNT # usally just the username without domain +--smtp-pass=PASSPHRASE +@end example + +If you are using a forwarding e-mail, such +as @@member.fsf.org, you send from using your +normal e-mail, but use the forwarding e-mail +address as the envelop-sender, most e-mail +server should accept this. + -- cgit v1.2.3-70-g09d2