From: "Tuncer Ayaz" <tuncer.ayaz@gmail.com>
To: "Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Q] submitting patches from gmail
Date: Sat, 18 Oct 2008 15:00:37 +0200 [thread overview]
Message-ID: <4ac8254d0810180600t7e06d05ya635d60c3e8ec8e6@mail.gmail.com> (raw)
In-Reply-To: <gdcm3d$f3k$1@ger.gmane.org>
On Sat, Oct 18, 2008 at 2:50 PM, Giuseppe Bilotta
<giuseppe.bilotta@gmail.com> wrote:
> On Saturday 18 October 2008 14:08, Leo Razoumov wrote:
>
>> Hi Everyone,
>> I wonder what is the preferred way to submit patches from a gmail account.
>> Google mail auto wraps long lines and there is no way to change this setting.
>> Safe way would be to use attachments. Are they allowed on git mailing list?
>
> I've been sending patches from gmail for a while without problems. It took me
> a while to find a working configruation, but I finally managed to do it using
> msmtp. I have
>
> [sendemail]
> smtpserver = /usr/bin/msmtp
>
> in my ~/.gitconfig
>
> and the following ~/.msmtprc
>
> ======
> # Example for a user configuration file
>
> # Set default values for all following accounts.
> defaults
> tls on
> tls_trust_file /etc/ssl/certs/ca-certificates.crt
> logfile ~/.msmtp.log
>
> # My email service
> account gmail
> host smtp.gmail.com
> from yourgmailusername@gmail.com
> auth on
> user yourgmailusername
> password yourgmailpassword
as the password is stored in plaintext I prefer
to leave it out and get asked every time I
use mstmp :-).
> # Set a default account
> account default : gmail
> =========
>
> And to send patches I just use something like
>
> git send-email --to "git@vger.kernel.org" --cc "whoever" 00*
next prev parent reply other threads:[~2008-10-18 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 12:08 [Q] submitting patches from gmail Leo Razoumov
2008-10-18 12:16 ` Tuncer Ayaz
2008-10-18 12:50 ` Giuseppe Bilotta
2008-10-18 13:00 ` Tuncer Ayaz [this message]
2008-10-18 14:12 ` Leo Razoumov
2008-10-18 14:20 ` Felipe Contreras
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=4ac8254d0810180600t7e06d05ya635d60c3e8ec8e6@mail.gmail.com \
--to=tuncer.ayaz@gmail.com \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
/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).