From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Kernel.org Tools" <tools@linux.kernel.org>,
Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Follow Upper <follow.upper@example.org>,
Cover Upper <cover.upper@example.org>,
Test Override <test-override@example.com>
Subject: Re: [PATCH b4 0/2] trailers: accept recognized link trailers + "Closes"
Date: Fri, 26 May 2023 13:46:29 -0400 [thread overview]
Message-ID: <168512318956.1381718.10679205841484797842.b4-ty@linuxfoundation.org> (raw)
In-Reply-To: <20230525-closes-tags-v1-0-ed41b1773cb6@tessares.net>
On Thu, 25 May 2023 22:10:35 +0200, Matthieu Baerts wrote:
> Nick reported in [1] that Closes tags were not picked up by b4 when
> updating trailers.
>
> In fact, it looks like that even Link ones were not picked up. (Or at
> least it was not working when I was testing it :) ).
>
> With this series, Link, BugLink and Closes tags are now automatically
> added when available in follow-up comments.
>
> [...]
Applied, thanks!
[1/2] trailers: accept recognized link trailers
commit: 0a6be433883dee544b991e218e0f505dba356a88
[2/2] trailers: add 'Closes' as recognized link trailer
commit: d21bd9e7ff99736818af68b99d36a8e77889132d
Best regards,
--
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
prev parent reply other threads:[~2023-05-26 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 20:10 [PATCH b4 0/2] trailers: accept recognized link trailers + "Closes" Matthieu Baerts
2023-05-25 20:10 ` [PATCH b4 1/2] trailers: accept recognized link trailers Matthieu Baerts
2023-05-25 20:10 ` [PATCH b4 2/2] trailers: add 'Closes' as recognized link trailer Matthieu Baerts
2023-05-26 17:46 ` Konstantin Ryabitsev [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=168512318956.1381718.10679205841484797842.b4-ty@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=cover.upper@example.org \
--cc=follow.upper@example.org \
--cc=matthieu.baerts@tessares.net \
--cc=ndesaulniers@google.com \
--cc=test-override@example.com \
--cc=tools@linux.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.