From: Javier Domingo Cansino <javierdo1@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: "Junio C Hamano" <gitster@pobox.com>, 惠轶群 <huiyiqun@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [GSoC] A late proposal: a modern send-email
Date: Mon, 28 Mar 2016 00:31:27 +0100 [thread overview]
Message-ID: <CALZVapn9KjXCpO+zaYuB6RSnG747u4a7e_m_HDg+uH-uz8UhQg@mail.gmail.com> (raw)
In-Reply-To: <20160327220002.GA29057@dcvr.yhbt.net>
> While Gmail provides SMTP access, it was (last I was told)
> incompatible with two-factor auth; so I've encountered users
> unable to send patches with their normal 2FA-enabled accounts.
>
> Maybe git hackers at Google have enough pull to lobby Gmail's
> web interface to make it easier to send plain-text patches;
> but I would love more to see users running local mail clients
> and even running their own SMTP servers.
Just in case, I use git send email with my gmail account and I have 2
step auth configured. The only "limitation" however is that you have
to create a password for each email client on it's own. If you own a
gmail account, go to
https://security.google.com/settings/security/apppasswords to create a
password for the email client.
--
Javier Domingo Cansino
next prev parent reply other threads:[~2016-03-27 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 17:59 [GSoC] A late proposal: a modern send-email 惠轶群
2016-03-25 18:16 ` Junio C Hamano
2016-03-26 2:13 ` 惠轶群
2016-03-26 6:18 ` Pranit Bauva
2016-03-26 9:52 ` 惠轶群
2016-03-26 10:18 ` 惠轶群
2016-03-26 10:21 ` 惠轶群
2016-03-28 16:49 ` Ævar Arnfjörð Bjarmason
2016-03-29 4:17 ` 惠轶群
2016-03-29 23:47 ` Ævar Arnfjörð Bjarmason
2016-03-30 12:10 ` Johannes Schindelin
2016-03-27 22:00 ` Eric Wong
2016-03-27 23:31 ` Javier Domingo Cansino [this message]
2016-03-28 13:00 ` 惠轶群
2016-04-05 0:03 ` Eric Wong
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALZVapn9KjXCpO+zaYuB6RSnG747u4a7e_m_HDg+uH-uz8UhQg@mail.gmail.com \
--to=javierdo1@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=huiyiqun@gmail.com \
--cc=normalperson@yhbt.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).