tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Greg Kroah-Hartman <greg@kroah.com>
Cc: users@linux.kernel.org, tools@linux.kernel.org,
	Johan Hovold <johan@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: b4 seems to be dropping "cc: stable" on patches.
Date: Mon, 19 Oct 2020 08:43:25 -0400	[thread overview]
Message-ID: <20201019124325.r5kx3yq3kqounke5@chatter.i7.local> (raw)
In-Reply-To: <20201019072006.GB3219053@kroah.com>

On Mon, Oct 19, 2020 at 09:20:06AM +0200, Greg Kroah-Hartman wrote:
> Hi Konstantin,
> 
> It looks like 'b4' is dropping the cc: stable lines of patches.

Correct, sorry about that -- I was trying to tighten trailer recognition 
to avoid hitting some of the false-positives I've seen and apparently 
this affected Cc: and Link: trailers. :(

This is currently fixed.

> I can reproduce this on the current b4 git tree, at commit c0910ee77a2a
> ("Fix header encoding introduced by earlier fix") as of this moment.

This is one of the dangers of the devel branch, unfortunately -- 
sometimes it ends up with half-baked code. I do need to finally put a 
solid test matrix in place, which is the target for 0.7.0 -- currently 
I'm just continuously running on lkml to find crashers, but it's not a 
good enough solution for finding formatting errors. So, the hope is that 
we'll learn to avoid regressions like this one in the near future.

-K

  reply	other threads:[~2020-10-19 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  7:20 b4 seems to be dropping "cc: stable" on patches Greg KH
2020-10-19 12:43 ` Konstantin Ryabitsev [this message]
2020-10-19 13:17   ` Greg KH

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=20201019124325.r5kx3yq3kqounke5@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=greg@kroah.com \
    --cc=johan@kernel.org \
    --cc=sashal@kernel.org \
    --cc=tools@linux.kernel.org \
    --cc=users@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).