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>] [day] [month] [year] [list]
Message-Id: <20171107.084535.1468386023963515204.davem@davemloft.net>
Date:   Tue, 07 Nov 2017 08:45:35 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     kurup.manish@...il.com
Cc:     jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
        jakub.kicinski@...ronome.com, pieter.jansenvanvuuren@...ronome.com,
        simon.horman@...ronome.com, john.hurley@...ronome.com,
        aring@...atatu.com, mrv@...atatu.com, manish.kurup@...izon.com,
        netdev@...r.kernel.org, oss-drivers@...ronome.com
Subject: Re: [PATCH net-next v6 0/3] Incorporated all required changes

From: Manish Kurup <kurup.manish@...il.com>
Date: Mon, 6 Nov 2017 11:52:37 -0500

> Currently, the body of the commit message describes what it is doing
> in each commit patch. Would you like me to add some detail to the
> description of each commit?

This is not what I am asking for.

The header posting for a patch series serves a very important
purpose.  It tells the reader at a high level what the patch
series is doing as a whole, how it is doing it, and why it is
doing it that way.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ