From: Dan Aloni <da-x@monatomic.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] automatic CC generation for patch submission
Date: Sat, 30 Jun 2007 13:47:52 +0300 [thread overview]
Message-ID: <20070630104752.GA26138@localdomain> (raw)
In-Reply-To: <20070630025425.59cbc299.akpm@linux-foundation.org>
On Sat, Jun 30, 2007 at 02:54:25AM -0700, Andrew Morton wrote:
> On Fri, 29 Jun 2007 19:51:53 -0700 "Kok, Auke" <auke-jan.h.kok@intel.com> wrote:
>
> > > Some extensions to the popular E-Mail clients might be needed
> > > here. Also, a bot reading LKML would automatically send links
> > > about posted patches to the other mailing lists whenever
> > > someone forgets to add a CC.
> > >
> > > Any comments?
> >
> > an easier way to implement this is to add an extra field in the MAINTAINERS
> > file, something like below. All the contact info would stay the same, closely
> > where applicable and it would allow you to also specify specific files as well.
>
> We already have that information in git. Parse the git changelogs of the
> affected files, find out who works on them.
I think it's quite complex to make a reliable inference of maintainership
information from git. Given a set of historical modifiers of a file,
would you take the most common commiter(s), or the most common
_recent_ commiter(s), or what? It's a bit fuzzy.
Moreover, it is slow in comparison and assumes the availability of
local .git db, which wouldn't be the case for some porition of patch
submitters.
> Not that it'll help much, given the amnount of stuff which gets
> mysteriously ignored even when the correct people are cc'ed...
Hopefully it gets ignored if it is quite low in priority. In that
case the CC is a NOP but might still be good for archiving purposes.
> (For extra giggles we could parse emailed oops and bug reports and add the
> appropriate cc's there too. Harder.)
BTS was discussed to death already, let's not delve into that...
--
Dan Aloni
XIV LTD, http://www.xivstorage.com
da-x (at) monatomic.org, dan (at) xiv.co.il
next prev parent reply other threads:[~2007-06-30 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 2:34 [RFC] automatic CC generation for patch submission Dan Aloni
2007-06-30 2:51 ` Kok, Auke
2007-06-30 3:10 ` Satyam Sharma
2007-06-30 3:29 ` Satyam Sharma
2007-06-30 9:54 ` Andrew Morton
2007-06-30 10:47 ` Dan Aloni [this message]
2007-06-30 16:32 ` Andrew Morton
2007-06-30 17:20 ` Adrian Bunk
2007-06-30 17:21 ` Dan Aloni
2007-06-30 14:33 ` Kok, Auke
2007-06-30 3:01 ` Oleg Verych
2007-06-30 3:08 ` Dan Aloni
2007-06-30 10:22 ` Oleg Verych
2007-06-30 10:26 ` Dan Aloni
2007-06-30 11:03 ` Oleg Verych
2007-06-30 4:01 ` Adrian Bunk
2007-06-30 9:47 ` Dan Aloni
2007-06-30 12:26 ` Adrian Bunk
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=20070630104752.GA26138@localdomain \
--to=da-x@monatomic.org \
--cc=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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