From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: devel@lists.elisa.tech,
"Ralf Ramsauer" <ralf.ramsauer@oth-regensburg.de>,
"Wolfgang Mauerer" <wolfgang.mauerer@oth-regensburg.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Pia Eichinger" <pia.eichinger@st.oth-regensburg.de>,
"Başak Erdamar" <basakerdamar@gmail.com>
Subject: Re: Small student project idea on appropriate integration trees in MAINTAINERS
Date: Thu, 28 Jan 2021 16:54:47 -0700 [thread overview]
Message-ID: <20210128165447.3da0d98e@lwn.net> (raw)
In-Reply-To: <CAKXUXMyRAer=0S9pxiRs2iF3pdkU8zW=JZw2a+nJJ30iPLPhCA@mail.gmail.com>
On Fri, 22 Jan 2021 09:22:24 +0100
Lukas Bulwahn <lukas.bulwahn@gmail.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
next prev parent reply other threads:[~2021-01-28 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 8:22 Small student project idea on appropriate integration trees in MAINTAINERS Lukas Bulwahn
2021-01-28 23:54 ` Jonathan Corbet [this message]
2021-02-05 6:42 ` Lukas Bulwahn
2021-02-05 14:06 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210128165447.3da0d98e@lwn.net \
--to=corbet@lwn.net \
--cc=basakerdamar@gmail.com \
--cc=devel@lists.elisa.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=pia.eichinger@st.oth-regensburg.de \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=wolfgang.mauerer@oth-regensburg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox