tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Greg KH" <greg@kroah.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org,
	Johan Hovold <johan@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: b4 seems to be dropping "cc: stable" on patches.
Date: Mon, 19 Oct 2020 09:20:06 +0200	[thread overview]
Message-ID: <20201019072006.GB3219053@kroah.com> (raw)

Hi Konstantin,

It looks like 'b4' is dropping the cc: stable lines of patches.

Or at least it currently does this for me when I do the following:

$ b4 am -t https://lore.kernel.org/r/20200921135951.24045-3-johan@kernel.org
Looking up https://lore.kernel.org/r/20200921135951.24045-3-johan%40kernel.org
Grabbing thread from lore.kernel.org/linux-usb
Analyzing 22 messages in the thread
---
Writing ./v2_20200921_johan_usb_cdc_acm_handle_broken_union_descriptors.mbx
  [PATCH v2 1/4] Revert "cdc-acm: hardening against malicious devices"
    + Acked-by: Oliver Neukum <oneukum@suse.com>
  [PATCH v2 2/4] USB: cdc-acm: handle broken union descriptors
    + Tested-by: Daniel Caujolle-Bert <f1rmb.daniel@gmail.com>
    + Acked-by: Oliver Neukum <oneukum@suse.com>
  [PATCH v2 3/4] USB: cdc-acm: use common data-class define
    + Acked-by: Oliver Neukum <oneukum@suse.com>
  [PATCH v2 4/4] USB: cdc-acm: clean up no-union-descriptor handling
    + Acked-by: Oliver Neukum <oneukum@suse.com>
---
Total patches: 4
---
Cover: ./v2_20200921_johan_usb_cdc_acm_handle_broken_union_descriptors.cover
 Link: https://lore.kernel.org/r/20200921135951.24045-1-johan@kernel.org
 Base: not found
       git am ./v2_20200921_johan_usb_cdc_acm_handle_broken_union_descriptors.mbx

If you look at the mbox, the "cc: stable" is now gone from the
signed-off-by area of the patch.

Johan just noticed this in this discussion of a patch that was "auto
selected" for stable backporting:
	https://lore.kernel.org/linux-usb/20201019070218.GO26280@localhost/

And as I've been using b4 for a few weeks now to apply patches, I don't
know where else this has dropped things :(

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

thanks,

greg k-h

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  7:20 Greg KH [this message]
2020-10-19 12:43 ` b4 seems to be dropping "cc: stable" on patches Konstantin Ryabitsev
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=20201019072006.GB3219053@kroah.com \
    --to=greg@kroah.com \
    --cc=johan@kernel.org \
    --cc=konstantin@linuxfoundation.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).