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]
Message-ID: <5418fb0b-47e2-d251-a6c7-a9bacbaf3dc1@gmail.com>
Date:   Tue, 5 Jul 2022 08:13:31 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Linux Documentation List <linux-doc@...r.kernel.org>,
        kernel test robot <lkp@...el.com>,
        Jonathan Corbet <corbet@....net>,
        Andrea Merello <andrea.merello@....it>,
        Jonathan Cameron <jic23@...nel.org>,
        Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Rob Herring <robh+dt@...nel.org>,
        Matt Ranostay <matt.ranostay@...sulko.com>,
        Alexandru Ardelean <ardeleanalex@...il.com>,
        jmondi <jacopo@...ndi.org>,
        linux-iio <linux-iio@...r.kernel.org>,
        devicetree <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] Documentation: bno055: separate SPDX identifier and
 page title

On 7/5/22 02:49, Andy Shevchenko wrote:
>> Cc: Jonathan Corbet <corbet@....net>
>> Cc: Andrea Merello <andrea.merello@....it>
>> Cc: Jonathan Cameron <jic23@...nel.org>
>> Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
>> Cc: Lars-Peter Clausen <lars@...afoo.de>
>> Cc: Rob Herring <robh+dt@...nel.org>
>> Cc: Matt Ranostay <matt.ranostay@...sulko.com>
>> Cc: Alexandru Ardelean <ardeleanalex@...il.com>
>> Cc: jacopo@...ndi.org
>> Cc: linux-iio@...r.kernel.org
>> Cc: devicetree@...r.kernel.org
>> Cc: linux-kernel@...r.kernel.org (open list)
> 
> It's a very noisy Cc list which will go in the git history. Instead,
> use --to and --cc parameters of `git format-patch`. Maintainers
> usually use `b4` tool that adds a Link tag to the patch itself on the
> Lore archive which will keep track on the Cc list anyway.
> 

Hi Andy,

Thanks for reminding me.

I think something like `b4 am -l`, right?

Anyway, should I resend (reroll)?

-- 
An old man doll... just what I always wanted! - Clara

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ