From: Junio C Hamano <gitster@pobox.com>
To: Aditya Garg <gargaditya08@live.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] send-email: pass smtp hostname and port to Authen::SASL
Date: Thu, 05 Mar 2026 06:44:55 -0800 [thread overview]
Message-ID: <87ldg6jpy0.fsf@gitster.g> (raw)
In-Reply-To: <MAUPR01MB11546AED093D8641767AACEFCB87DA@MAUPR01MB11546.INDPRD01.PROD.OUTLOOK.COM> (Aditya Garg's message of "Thu, 5 Mar 2026 12:06:21 +0000")
Aditya Garg <gargaditya08@live.com> writes:
[administrivia]
Please do not send patch e-mails directly at me, unless you know
that I am the area authority. Initial submissions are better
sent to the list on To: list, with area experts on Cc: if you
know or found out who they are.
> Starting from version 2.2000, Authen::SASL supports passing the SMTP
> server hostname and port to the OAUTHBEARER string passed via SMTP AUTH.
> Add support for the same in git-send-email.
The proposed log message should answer these questions as well:
What happens with version before 2.2000? Is it safe to
unconditionally add parameters like this patch does, and why?
> Link: https://metacpan.org/pod/Authen::SASL::Perl::OAUTHBEARER
>
> Signed-off-by: Aditya Garg <gargaditya08@live.com>
> ---
> git-send-email.perl | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/git-send-email.perl b/git-send-email.perl
> index eed5420882..0ac4d634e8 100755
> --- a/git-send-email.perl
> +++ b/git-send-email.perl
> @@ -1474,6 +1474,8 @@ sub smtp_auth_maybe {
> user => $cred->{'username'},
> pass => $cred->{'password'},
> authname => $cred->{'username'},
> + host => $smtp_server,
> + (defined $smtp_server_port ? (port => $smtp_server_port) : ()),
> }
> );
> $result = $smtp->auth($sasl);
Thanks.
next prev parent reply other threads:[~2026-03-05 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 12:06 [PATCH] send-email: pass smtp hostname and port to Authen::SASL Aditya Garg
2026-03-05 14:44 ` Junio C Hamano [this message]
2026-03-05 15:14 ` Aditya Garg
2026-03-05 16:24 ` Junio C Hamano
2026-03-05 16:54 ` Aditya Garg
2026-03-05 17:01 ` [PATCH v2] " Aditya Garg
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=87ldg6jpy0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=gargaditya08@live.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.