linux-kernel - Re: Small student project idea on appropriate integration trees in MAINTAINERS

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:   Thu, 28 Jan 2021 16:54:47 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc:     devel@...ts.elisa.tech,
        Ralf Ramsauer <ralf.ramsauer@...-regensburg.de>,
        Wolfgang Mauerer <wolfgang.mauerer@...-regensburg.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Pia Eichinger <pia.eichinger@...oth-regensburg.de>,
        Başak Erdamar <basakerdamar@...il.com>
Subject: Re: Small student project idea on appropriate integration trees in
 MAINTAINERS

On Fri, 22 Jan 2021 09:22:24 +0100
Lukas Bulwahn <lukas.bulwahn@...il.com> wrote:

> In this project, we can make use of:
> 
> - gitdm [git://git.lwn.net/gitdm.git]: gitdm includes some scripts to
> parse MAINTAINERS and obtain the integration tree patch of a commit.

Look also at the 'treeplot' tool there, which determines which tree(s)
each patch went through and makes pretty (OK, not hugely pretty) pictures
from the result.

I suspect you'll find that the tree information is mostly correct.
Developers need to know that to be able to base their patches properly; an
incorrect entry would lead to a certain amount of maintainer misery.

Thanks,

jon