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] [day] [month] [year] [list]
Message-ID: <AM5PR0501MB213276AEE1C2B72C525C831CAB820@AM5PR0501MB2132.eurprd05.prod.outlook.com>
Date:   Wed, 16 Aug 2017 03:38:54 +0000
From:   Chris Mi <chrism@...lanox.com>
To:     David Miller <davem@...emloft.net>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [patch net-next 0/3] net/sched: Improve getting objects by
 indexes

Hi David,

Thanks for your suggestion.  If needed, I could send the review request again
without so long CC: list.  I surely will avoid such mistake in the future.

Thanks,
Chris

> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Wednesday, August 16, 2017 11:06 AM
> To: Chris Mi <chrism@...lanox.com>
> Cc: netdev@...r.kernel.org
> Subject: Re: [patch net-next 0/3] net/sched: Improve getting objects by
> indexes
> 
> 
> The CC: list you used for these postings was way too large.
> 
> Seriously, netdev by itself or with one or two _specific_ developers added
> would have been more than sufficient.
> 
> If you are automating things using the MAINTAINERS file, always look over
> the result by hand and ask yourself "Do I really have to
> CC: everything listed in this thing?"
> 
> Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ