From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>, tools@linux.kernel.org
Subject: Re: b4 strips BiugLink
Date: Wed, 9 Dec 2020 12:10:30 -0500 [thread overview]
Message-ID: <20201209171030.hztkqs5ych62dvck@chatter.i7.local> (raw)
In-Reply-To: <20201209165356.GT4077@smile.fi.intel.com>
On Wed, Dec 09, 2020 at 06:53:56PM +0200, Andy Shevchenko wrote:
> > > Okay, there is a fix in master and stable-0.6.y that adds BugLink
> > > to the
> > > list.
> >
> > Wow that's quick!
> >
> > Thanks a lot Konstantin!
>
> Thanks!
>
> Btw, can b4 print a warning if it cuts an (unknown) tag?
I can actually improve on the algorithm. We only need to be cautious
about stuff sent as follow-ups -- anything that is part of the commit
message already doesn't need to be scrutinized.
I'll put in a fix that just accepts trailers seen in patch series itself
without checking.
-K
prev parent reply other threads:[~2020-12-09 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 8:13 b4 strips BiugLink Linus Walleij
2020-12-09 10:24 ` Andy Shevchenko
2020-12-09 13:19 ` Konstantin Ryabitsev
2020-12-09 14:40 ` Linus Walleij
2020-12-09 16:53 ` Andy Shevchenko
2020-12-09 17:10 ` 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=20201209171030.hztkqs5ych62dvck@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--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).