From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Gmail OAuth2 in git send-email
Date: Thu, 3 Jun 2021 14:08:51 -0400 [thread overview]
Message-ID: <20210603180851.5tbnuvfb6auxrhvm@nitro.local> (raw)
In-Reply-To: <d93a3024-ba8d-3469-2dba-2e0032334232@gmail.com>
On Thu, Jun 03, 2021 at 12:02:08PM +0700, Bagas Sanjaya wrote:
> But for users that use Gmail (like me), we must either enable 2FA and
> generate app-specific password for use with git send-email
Is there a general problem with this approach? Gmail has been my
recommendation for everyone needing a free email account -- it's still
possible to configure it to be perfectly usable with patch-based workflows,
even if it has its own ideas about web ui treading.
The fact that Gmail forces folks to enable 2fa for app passwords is an added
bonus in my book. :)
There are other alternatives, but they are not gratis or don't work well for
sending patches. I'm also aware that gmail is not reliable for certain
geographical locales, so it's not a solution that suits everyone. We have
recently partnered with migadu.com and will start providing email accounts for
Linux devs who cannot reliably use any other solution either due to their
employer doing nasty things to outgoing mail, or some other reason. At $20 a
year, migadu's pricing is hard to beat, though I know it's not for everyone.
-K
next prev parent reply other threads:[~2021-06-03 18:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 5:02 Gmail OAuth2 in git send-email Bagas Sanjaya
2021-06-03 5:48 ` ZheNing Hu
2021-06-03 6:08 ` Jonathan Nieder
2021-06-03 6:26 ` Eric Sunshine
2021-06-03 8:28 ` Ævar Arnfjörð Bjarmason
2021-06-03 17:46 ` Felipe Contreras
2021-06-03 18:21 ` Andreas Schwab
2021-06-03 19:01 ` Felipe Contreras
2021-06-04 1:49 ` Jonathan Nieder
2021-06-04 2:39 ` Jonathan Nieder
2021-06-04 3:44 ` Felipe Contreras
2021-06-03 18:08 ` Konstantin Ryabitsev [this message]
2021-06-03 18:25 ` Eric Sunshine
2021-06-03 18:32 ` Konstantin Ryabitsev
2021-06-03 19:02 ` Michal Suchánek
2021-06-03 19:07 ` Konstantin Ryabitsev
2021-06-03 19:23 ` Michal Suchánek
2021-06-03 23:42 ` Eric Sunshine
2021-06-03 19:06 ` Felipe Contreras
2021-06-03 23:35 ` Eric Sunshine
2021-06-04 1:11 ` Felipe Contreras
2021-06-04 1:49 ` Đoàn Trần Công Danh
2021-06-04 2:07 ` Felipe Contreras
2021-06-04 2:11 ` Đoàn Trần Công Danh
2021-06-04 3:45 ` Felipe Contreras
2021-06-04 5:21 ` Đoàn Trần Công Danh
2021-06-04 6:00 ` Felipe Contreras
2021-06-04 6:23 ` Đoàn Trần Công Danh
2021-06-04 13:32 ` Felipe Contreras
2021-06-04 4:10 ` Eric Sunshine
2021-06-04 5:35 ` 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=20210603180851.5tbnuvfb6auxrhvm@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=bagasdotme@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).