From: Tomas Melin <tomas.melin@vaisala.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
"Kernel.org Tools" <tools@kernel.org>
Subject: Re: [PATCH b4 0/2] Add support for oauth2 SMTP authentication
Date: Thu, 5 Feb 2026 11:18:56 +0200 [thread overview]
Message-ID: <9817b09b-2ef0-4fad-ad76-bb746a5df858@vaisala.com> (raw)
In-Reply-To: <20260201-sceptical-resolute-curassow-43ab98@lemur>
Hi,
On 01/02/2026 07:52, Konstantin Ryabitsev wrote:
> On Sun, Feb 01, 2026 at 12:37:34AM -0500, Konstantin Ryabitsev wrote:
>> On Thu, 29 Jan 2026 11:10:28 +0200, Tomas Melin <tomas.melin@vaisala.com> wrote:
>>> Add support for oauth2 authentication with SMTP server, integrating
>>> with git credential helpers for retrieving tokens. With this approach,
>>> the same configuration as is needed for git send-email can be used
>>> to send patches using oauth2 with b4.
>>
>> Thank you for sending this in! I'm using this series as a guinea pig for
>> the "b4 review" functionality, using agent-assisted reviews. I know it's
>> not everyone's cup of tea, but there is enough interest in it to at
>> least support it.
>>
>> I'm sending per-patch followups with the problems the agent has
>> identified (combed by myself -- I'm not just blindly relying on the
>> agent here).
>>
>> I am also screencasting this whole process, so hopefully this will be
>> educational as well. :)
>
> This is the screencast:
> https://asciinema.org/a/777545
>
Thanks for sharing! Interesting stuff and looks promising.
FYI for upcoming v2 I have also reviewed the patches with an agent, so
let's see if they agree about possible findings :)
thanks,
Tomas
> There are still lots of improvements to "b4 review" to consider it useful and
> remotely maintainer-ready, but it's at least doing useful things already.
>
> Cheers,
> -K
prev parent reply other threads:[~2026-02-05 9:19 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
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 [this message]
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=9817b09b-2ef0-4fad-ad76-bb746a5df858@vaisala.com \
--to=tomas.melin@vaisala.com \
--cc=konstantin@linuxfoundation.org \
--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