From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: Inquiry around 'b4 send' individual patch Cc's
Date: Tue, 3 Jan 2023 17:40:32 -0500 [thread overview]
Message-ID: <20230103224032.dpy26yvpebbxndyq@meerkat.local> (raw)
In-Reply-To: <Y6zeRaKlqNhh72OD@dev-arch.thelio-3990X>
On Wed, Dec 28, 2022 at 05:24:37PM -0700, Nathan Chancellor wrote:
> Hi Konstantin,
> This appears to work for me but I noticed that if there are multiple
> patches that need to be Cc'd to the same people in the series, they are
> not deduplicated for the cover letter. For example, I see the following
> output with 'b4 prep -d' for this series, which has two MIPS patches,
> three PowerPC patches, and three s390 patches, which all include the
> exact same trailers generated from scripts/get_maintainer.pl:
>
> | To: Masahiro Yamada <masahiroy@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>
> | Cc: Nicolas Schier <nicolas@fjasle.eu>, Tom Rix <trix@redhat.com>, linux-kbuild@vger.kernel.org,
> | llvm@lists.linux.dev, Nathan Chancellor <nathan@kernel.org>, kernel test robot <lkp@intel.com>,
> | Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
> | Dave Hansen <dave.hansen@linux.intel.com>, x86@kernel.org, Arvind Sankar <nivedita@alum.mit.edu>,
> | Thomas Bogendoerfer <tsbogend@alpha.franken.de>, linux-mips@vger.kernel.org,
> | Thomas Bogendoerfer <tsbogend@alpha.franken.de>, linux-mips@vger.kernel.org,
> | Michael Ellerman <mpe@ellerman.id.au>, Nicholas Piggin <npiggin@gmail.com>,
> | Christophe Leroy <christophe.leroy@csgroup.eu>, linuxppc-dev@lists.ozlabs.org,
> | Michael Ellerman <mpe@ellerman.id.au>, Nicholas Piggin <npiggin@gmail.com>,
> | Christophe Leroy <christophe.leroy@csgroup.eu>, linuxppc-dev@lists.ozlabs.org,
> | Michael Ellerman <mpe@ellerman.id.au>, Nicholas Piggin <npiggin@gmail.com>,
> | Christophe Leroy <christophe.leroy@csgroup.eu>, linuxppc-dev@lists.ozlabs.org,
> | Heiko Carstens <hca@linux.ibm.com>, Vasily Gorbik <gor@linux.ibm.com>,
> | Alexander Gordeev <agordeev@linux.ibm.com>, Christian Borntraeger <borntraeger@linux.ibm.com>,
> | Sven Schnelle <svens@linux.ibm.com>, linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
> | Vasily Gorbik <gor@linux.ibm.com>, Alexander Gordeev <agordeev@linux.ibm.com>,
> | Christian Borntraeger <borntraeger@linux.ibm.com>, Sven Schnelle <svens@linux.ibm.com>,
> | linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>, Vasily Gorbik <gor@linux.ibm.com>,
> | Alexander Gordeev <agordeev@linux.ibm.com>, Christian Borntraeger <borntraeger@linux.ibm.com>,
> | Sven Schnelle <svens@linux.ibm.com>, linux-s390@vger.kernel.org, Harry Wentland <harry.wentland@amd.com>,
> | Leo Li <sunpeng.li@amd.com>, Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
> | Alex Deucher <alexander.deucher@amd.com>, Christian König <christian.koenig@amd.com>,
> | "Pan, Xinhui" <Xinhui.Pan@amd.com>, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
>
Eeek. This should be fixed now with the latest commit in master and
stable-0.11.y. Thank you for the report!
I should have a 0.11.2 out in the next day or two.
-K
prev parent reply other threads:[~2023-01-03 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 0:24 Inquiry around 'b4 send' individual patch Cc's Nathan Chancellor
2023-01-03 22:40 ` 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=20230103224032.dpy26yvpebbxndyq@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=nathan@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).