linux-kernel - Re: [PATCH 00/18] use semicolons rather than commas to separate statements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 3 Oct 2020 21:18:51 +0200 (CEST)
From:   Julia Lawall <julia.lawall@...ia.fr>
To:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>
cc:     Joe Perches <joe@...ches.com>, Mark Brown <broonie@...nel.org>,
        tools@...ux.kernel.org, linux-iio@...r.kernel.org,
        Julia Lawall <Julia.Lawall@...ia.fr>,
        linux-stm32@...md-mailman.stormreply.com,
        linux-crypto@...r.kernel.org,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
        Jerome Brunet <jbrunet@...libre.com>,
        linux-acpi@...r.kernel.org, David Lechner <david@...hnology.com>,
        Valdis Klētnieks <valdis.kletnieks@...edu>,
        kernel-janitors@...r.kernel.org, drbd-dev@...ts.linbit.com,
        openipmi-developer@...ts.sourceforge.net,
        Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
        linux-ide@...r.kernel.org, linux-amlogic@...ts.infradead.org,
        linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-wireless@...r.kernel.org,
        Neil Armstrong <narmstrong@...libre.com>
Subject: Re: [PATCH 00/18] use semicolons rather than commas to separate
 statements



On Sat, 3 Oct 2020, Konstantin Ryabitsev wrote:

> On Sat, Oct 03, 2020 at 11:40:48AM -0700, Joe Perches wrote:
> > (Adding tools and Konstantin Ryabitsev)
> >
> > There seems to be some mismatch between b4's use of the
> > cover letter to a patch series and what maintainers that
> > apply a subset of the patches in the patch series.
> >
> > The merge description shows the entire patch series as
> > applied, but the actual merge is only a subset of the
> > series.
> >
> > Can this be improved in b4?
>
> So, the following logic should be applied:
>
> - if the entire series was applied, reply to 0/n
> - if a subset only is applied, reply to each n/n of the patch that was
>   cherry-picked out of the series
>
> Is that an accurate summary?

That sounds good.

julia