linux-ext4 - Re: Patch format in ext4 patch queue.

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]

Date:	Mon, 24 Sep 2007 23:34:06 +0200
From:	Karel Zak <kzak@...hat.com>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc:	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: Patch format in ext4 patch queue.

On Fri, Sep 21, 2007 at 04:03:26PM +0530, Aneesh Kumar K.V wrote:
> First line should be
> <subsystem_name>: A single line description of the patch.
> This appear in the subject line of the mail that results from different
> commit list.

 BTW, we use this subject format for util-linux-ng and I have a simple
 python script that generates nice changelogs (for release notes) from
 git log.

 IMHO a changelog [1] that is sorted and grouped by <subsystem_name>
 is better for end-users that output from git-shortlog.

    Karel

 [1] see Changelog section:
    ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.13/v2.13-ReleaseNotes

-- 
 Karel Zak  <kzak@...hat.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html