Hi, Bagas Sanjaya <bagasdotme@xxxxxxxxx> 于2021年6月3日周四 下午1:05写道： > > Hi, > > For most email providers, adding following .gitconfig is enough to > seamlessly use git send-email: > > > [sendemail] > > smtpEncryption = tls > > smtpServer = <server> > > smtpUser = <email> > > smtpServerPort = 587 > > But for users that use Gmail (like me), we must either enable 2FA and > generate app-specific password for use with git send-email, or enable > less-secure app access. That's because Gmail prefers authenticating with > OAuth2, but git send-email use plain text authentication instead. > > I personally prefer the latter because I know that I enabled less-secure > app access only for duration of sending patches with git send-email > (that is, I switched the trigger when I run git send-email). > > We wonder whether git send-email can support Gmail OAuth2 so that we can > seamlessly send patches without having to choose either action. But > however, we have to create a GCP project [1] first in order to enable > Gmail API. This can be overkill for some folks, but unfortunately that's > the only way. > > If we want to enable support for Gmail OAuth2, should we hands-off API > configuration to git send-email users, or should we configure it on > behalf of them? Note that when we go the former approach, some Gmail > users simply can't afford GCP pricing for whatever reason (even don't > have any of required payment methods), whereas the latter approach we > must cover that cost (and Software Freedom Conservancy can raise funds > needed for it or git.git developers can pay it). > I met the same question as you before. [1] (write by chinese) We need cumbersome operations to allow gmail to agree to use git send-email. I also want to know if send-email can be made more convenient (to reduce some configuration problems with gmail). [1]: https://adlternative.github.io/archlinux%E4%B8%8A%E7%9A%84git-send-email%E9%97%AE%E9%A2%98%E7%9A%84%E8%A7%A3%E5%86%B3%E6%96%B9%E6%A1%88/
