From: Joshua Watt <jpewhacker@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] send-email: explicitly disable authentication
Date: Thu, 18 Oct 2018 17:01:53 -0500 [thread overview]
Message-ID: <9dc2995ff84158450255478c7411339a81f63aba.camel@gmail.com> (raw)
In-Reply-To: <CAPig+cR27mPmH+0oeT+2T878K-cBNqBnxPUumETnVK1cvz2qnA@mail.gmail.com>
On Thu, 2018-10-18 at 17:53 -0400, Eric Sunshine wrote:
> On Thu, Oct 18, 2018 at 5:16 PM Joshua Watt <jpewhacker@gmail.com>
> wrote:
> > It can be necessary to disable SMTP authentication by a mechanism
> > other
> > than sendemail.smtpuser being undefined. For example, if the user
> > has
> > sendemail.smtpuser set globally but wants to disable authentication
> > locally in one repository.
> >
> > --smtp-auth and sendemail.smtpauth now understand the value 'none'
> > which
> > means to disable authentication completely, even if an
> > authentication
> > user is specified.
>
> Implementation complexity aside, spelling the option --no-smtp-auth
> might be more intuitive and consistent than --smtp-auth=none.
One advantage of --smtp-auth=none is that it can also be done with a
config variable sendemail.smtpauth="none". Would be also add a config
variable like sendemail.nosmtpauth (the negative seems strange to me)?
Or maybe --no-smtp-auth is just a shorthand alias for --smtp-auth=none?
>
> > The value 'none' is lower case to avoid conflicts with any RFC 4422
> > authentication mechanisms.
> >
> > Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
--
Joshua Watt <JPEWhacker@gmail.com>
next prev parent reply other threads:[~2018-10-18 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 21:15 [PATCH] send-email: explicitly disable authentication Joshua Watt
2018-10-18 21:53 ` Eric Sunshine
2018-10-18 22:01 ` Joshua Watt [this message]
2018-10-19 14:10 ` Eric Sunshine
2018-10-22 17:52 ` [PATCH v2] " Joshua Watt
2018-10-22 18:03 ` Joshua Watt
2018-10-23 0:32 ` Junio C Hamano
2018-10-23 2:40 ` Joshua Watt
2018-10-23 3:24 ` [PATCH v3] " Joshua Watt
2018-10-25 9:43 ` Junio C Hamano
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=9dc2995ff84158450255478c7411339a81f63aba.camel@gmail.com \
--to=jpewhacker@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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).