From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 Cc: lines
Date: Tue, 24 Nov 2020 17:27:56 -0500 [thread overview]
Message-ID: <20201124222756.osrv7ixjer6n3f3f@chatter.i7.local> (raw)
In-Reply-To: <20201014164747.GM3100363@kernel.org>
On Wed, Oct 14, 2020 at 01:47:47PM -0300, Arnaldo Carvalho de Melo wrote:
> First of all, thanks a lot for b4, I'm now using it regularly,
> great tool!
>
> My previous workflow involved a 'am' script that I would have to
> use patch by patch, would go on it and collect Cc: lines, not just the
> ones in the patch itself, but the ones in the e-mail containing it, as I
> wanted to record that that group of people was actually made aware of
> that change.
>
> Would it be possible to have something like a --cc to have that?
I added this feature to the latest master, but I'm not 100% sure if it's
doing the right/useful thing. If we only look for Cc: addresses, then
more often than not we just find mailing lists there:
----
$ b4 am -o/tmp 20201124143848.874894-1-antonio.borneo@st.com --cc-trailers
Looking up https://lore.kernel.org/r/20201124143848.874894-1-antonio.borneo%40st.com
Grabbing thread from lore.kernel.org/lkml
Analyzing 12 messages in the thread
Will use the latest revision: v2
You can pick other revisions using the -vN flag
---
Writing /tmp/v2_20201124_antonio_borneo_net_phy_realtek_read_actual_speed_on_rtl8211f_to_detect_downshift.mbx
✓ [PATCH v2] net: phy: realtek: read actual speed on rtl8211f to detect downshift
+ Cc: linuxarm@huawei.com
+ Cc: Salil Mehta <salil.mehta@huawei.com>
+ Cc: linux-stm32@st-md-mailman.stormreply.com
+ Cc: linux-kernel@vger.kernel.org
---
✓ Attestation-by: DKIM/st.com (From: antonio.borneo@st.com)
---
Total patches: 1
---
Link: https://lore.kernel.org/r/20201124215932.885306-1-antonio.borneo@st.com
Base: 9bd2702d292cb7b565b09e949d30288ab7a26d51
git checkout -b v2_20201124_antonio_borneo_st_com 9bd2702d292cb7b565b09e949d30288ab7a26d51
git am /tmp/v2_20201124_antonio_borneo_net_phy_realtek_read_actual_speed_on_rtl8211f_to_detect_downshift.mbx
----
Is it better to look both in To: and Cc:, or did you specifically intend
to have just the Cc: header copied into the commit?
I'm also a bit worried that on some patches the Cc trailer list ends up
fairly huge. Is that expected and okay?
-K
next parent reply other threads:[~2020-11-24 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201014164747.GM3100363@kernel.org>
2020-11-24 22:27 ` Konstantin Ryabitsev [this message]
2020-11-26 12:14 ` b4 Cc: lines acme
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=20201124222756.osrv7ixjer6n3f3f@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=acme@kernel.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 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.