public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Tomas Melin <tomas.melin@vaisala.com>
Cc: "Kernel.org Tools" <tools@kernel.org>
Subject: Re: [PATCH b4 2/2] b4: add support for oauth2 SMTP authentication
Date: Mon, 2 Feb 2026 22:31:22 -0500	[thread overview]
Message-ID: <20260202-amorphous-certain-walrus-e2bdd5@lemur> (raw)
In-Reply-To: <c06e3173-dbec-4e05-91d5-b087e3f69b22@vaisala.com>

On Mon, Feb 02, 2026 at 06:49:09PM +0200, Tomas Melin wrote:
> > Any reason we're not making use of git_credential_fill() here? I'm not sure we
> > can expect correct return here, because credential helpers expect input on
> > stdin like:
> > 
> >   protocol=smtp
> >   host=<server>
> >   username=<user>
> > 
> > The existing git_credential_fill() function should already handle this
> > correctly, unless I'm mistaken or you have other reasons not to use it.
> 
> Adding to my previous reply, this integration aligns with
> https://git-scm.com/docs/gitcredentials and in particular
> https://git-scm.com/docs/gitcredentials#_custom_helpers
> 
> And in identical manner as git-send-email this uses external helpers
> like listed here https://git-scm.com/docs/git-send-email#_sending_patches
> 
> So I don't see that git_credential_fill would be a match for it.

Sounds good to me, thank you for doing the extra legwork. I will be happy to
review v2 once you send it in with the other fixes.

-K

  reply	other threads:[~2026-02-03  3:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29  9:10 [PATCH b4 0/2] Add support for oauth2 SMTP authentication Tomas Melin
2026-01-29  9:10 ` [PATCH b4 1/2] ez: add SMTP authentication method to printed information Tomas Melin
2026-02-01  5:37   ` Konstantin Ryabitsev
2026-02-02 14:31     ` Tomas Melin
2026-01-29  9:10 ` [PATCH b4 2/2] b4: add support for oauth2 SMTP authentication Tomas Melin
2026-01-30 12:09   ` Tomas Melin
2026-02-01  5:37   ` Konstantin Ryabitsev
2026-02-02 14:08     ` Tomas Melin
2026-02-02 16:49     ` Tomas Melin
2026-02-03  3:31       ` Konstantin Ryabitsev [this message]
2026-02-01  5:37 ` [PATCH b4 0/2] Add " Konstantin Ryabitsev
2026-02-01  5:52   ` Konstantin Ryabitsev
2026-02-05  9:18     ` Tomas Melin

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=20260202-amorphous-certain-walrus-e2bdd5@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=tomas.melin@vaisala.com \
    --cc=tools@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