From: "Tuncer Ayaz" <tuncer.ayaz@gmail.com>
To: SLONIK.AZ@gmail.com
Cc: git@vger.kernel.org
Subject: Re: [Q] submitting patches from gmail
Date: Sat, 18 Oct 2008 14:16:43 +0200 [thread overview]
Message-ID: <4ac8254d0810180516h56633ed3q8377ddbbbf316bab@mail.gmail.com> (raw)
In-Reply-To: <ee2a733e0810180508m466f3ea1i9c63b47177f6e12d@mail.gmail.com>
On Sat, Oct 18, 2008 at 2:08 PM, Leo Razoumov <slonik.az@gmail.com> 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 do use git send-mail with msmtp as the SMTP client and smtp.gmail.com as
the host. If you are able to go that route it would solve your problem.
next prev parent reply other threads:[~2008-10-18 12:19 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 [this message]
2008-10-18 12:50 ` Giuseppe Bilotta
2008-10-18 13:00 ` Tuncer Ayaz
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=4ac8254d0810180516h56633ed3q8377ddbbbf316bab@mail.gmail.com \
--to=tuncer.ayaz@gmail.com \
--cc=SLONIK.AZ@gmail.com \
--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).