From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: "Kernel.org Tools" <tools@linux.kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Matthieu Baerts <matthieu.baerts@tessares.net>,
Follow Upper <follow.upper@example.org>,
Cover Upper <cover.upper@example.org>,
Test Override <test-override@example.com>
Subject: [PATCH b4 0/2] trailers: accept recognized link trailers + "Closes"
Date: Thu, 25 May 2023 22:10:35 +0200 [thread overview]
Message-ID: <20230525-closes-tags-v1-0-ed41b1773cb6@tessares.net> (raw)
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.
Link: https://lore.kernel.org/all/CAKwvOdm=Zk8YhrPptN3k7UQo+1n7Ws=Qox=BwTR9bbjPJJYz8A@mail.gmail.com/ [1]
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
---
Matthieu Baerts (2):
trailers: accept recognized link trailers
trailers: add 'Closes' as recognized link trailer
b4/__init__.py | 8 +++++---
tests/samples/trailers-thread-with-cover-followup.mbox | 2 ++
tests/samples/trailers-thread-with-cover-followup.verify | 2 ++
3 files changed, 9 insertions(+), 3 deletions(-)
---
base-commit: bfdf5b3b0835c8c351abbcd9b3b5268acf6545fa
change-id: 20230525-closes-tags-49d25abf4c24
Best regards,
--
Matthieu Baerts <matthieu.baerts@tessares.net>
next reply other threads:[~2023-05-25 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 20:10 Matthieu Baerts [this message]
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 ` [PATCH b4 0/2] trailers: accept recognized link trailers + "Closes" Konstantin Ryabitsev
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=20230525-closes-tags-v1-0-ed41b1773cb6@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=cover.upper@example.org \
--cc=follow.upper@example.org \
--cc=konstantin@linuxfoundation.org \
--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 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).