From: "Ted Ts'o" <tytso@mit.edu>
To: Joe Perches <joe@perches.com>
Cc: Florian Mickler <florian@mickler.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Hemminger <shemminger@vyatta.com>,
Wolfram Sang <w.sang@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: RFC: get_maintainer.pl: append reason for cc to the name by default
Date: Mon, 27 Sep 2010 16:47:56 -0400 [thread overview]
Message-ID: <20100927204756.GC3168@thunk.org> (raw)
In-Reply-To: <1285618097.1732.204.camel@Joe-Laptop>
On Mon, Sep 27, 2010 at 01:08:17PM -0700, Joe Perches wrote:
> On Mon, 2010-09-27 at 21:26 +0200, Florian Mickler wrote:
> > But we should definitely try to tune down the annoying part of
> > it by making it less random and maybe by adding a tag in the cc field...
>
> Less random: sure, whatever's reasonable.
>
> I still think that tagging the name portion of an email address
> is not a good idea, especially without some way of turning it
> off. Maybe a mechanism to optionally enable it would be ok.
Well, at the moment, what is currently shipping in git-head and 2.6.35
does such an __awful__ job that I think a lot of people would be a lot
happier if we could get the e-mail messages tagged. Maybe the call
for that would be less if some of queued fixes for get_maintainer.pl
could get pushed out more quickly, or you made an out-of-tree version
of get_mainatiner.pl so that fixes could get pushed to the newbies
more quickly.
Still, if as you argue, the heuristic guessing from the git repository
becomes something which will (eventually) be rarely done, then what
harm does it done if when those time that get_maintainer.pl is
guessing wildly by trying to read git history, those e-mail names are
tagged?
I'd argue that users shouldn't be using get_maintainer.pl in scripts.
Those who use them properly can always cut away the tags. If someone
is lazy enough to be using get_maintainer.pl in a script to send
e-mail, then I think it's only fair and transparent that the fact that
(a) they are using get_maintainer in a script, and (b)
get_maintainer.pl was forced to guess would be a good thing.
Think about it this way; if we see something to LKML with an a
get_maintainer.pl tag indicating that it had to guess, it's a hint
that the MAINTAINERS file needs to be updated? Wouldn't that be a
valuable way of notifying people of that fact? :-)
- Ted
next prev parent reply other threads:[~2010-09-27 20:48 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 9:33 [PATCH] get_maintainer.pl: append reason for cc to the name by default florian
2010-09-10 9:42 ` Joe Perches
2010-09-10 9:46 ` Wolfram Sang
2010-09-10 9:53 ` Mark Brown
2010-09-10 10:04 ` Joe Perches
2010-09-10 10:18 ` Mark Brown
2010-09-10 10:47 ` Joe Perches
2010-09-10 11:07 ` Mark Brown
2010-09-11 0:22 ` [PATCH] scripts/get_maintainer.pl: Add --git-blame --rolestats "Authored lines" information Joe Perches
2010-09-11 9:38 ` Florian Mickler
2010-09-11 9:52 ` Joe Perches
2010-09-11 10:02 ` Florian Mickler
2010-09-11 10:22 ` Joe Perches
2010-09-11 19:22 ` [PATCH] Documentation/SubmittingPatches: Add and describe scripts/get_maintainer.pl Joe Perches
2010-09-11 19:34 ` Florian Mickler
2010-09-11 19:43 ` [PATCH V2] " Joe Perches
2010-09-12 16:18 ` Florian Mickler
2010-09-10 11:44 ` [PATCH] get_maintainer.pl: append reason for cc to the name by default Alan Cox
2010-09-10 10:22 ` Florian Mickler
2010-09-10 10:47 ` Joe Perches
2010-09-11 21:22 ` Joe Perches
2010-09-10 10:30 ` Florian Mickler
2010-09-10 11:04 ` Mark Brown
2010-09-10 11:15 ` Florian Mickler
2010-09-10 21:04 ` Andrew Morton
2010-09-10 21:39 ` Florian Mickler
2010-09-10 21:44 ` Joe Perches
2010-09-13 4:01 ` Valdis.Kletnieks
2010-09-13 5:21 ` [PATCH] get_maintainer.pl: Look for .get_maintainer.conf in lk, then $HOME then scripts Joe Perches
2010-09-13 6:13 ` Florian Mickler
2010-09-13 13:21 ` Valdis.Kletnieks
2010-09-10 11:11 ` [PATCH] get_maintainer.pl: append reason for cc to the name by default Florian Mickler
2010-09-10 15:12 ` Joe Perches
2010-09-11 9:34 ` Florian Mickler
2010-09-11 0:13 ` Christoph Hellwig
2010-09-11 0:31 ` Joe Perches
2010-09-11 0:45 ` Christoph Hellwig
2010-09-11 0:56 ` Joe Perches
2010-09-11 9:28 ` Florian Mickler
2010-09-13 7:16 ` Eric W. Biederman
2010-09-13 7:57 ` Joe Perches
2010-09-13 8:54 ` Florian Mickler
2010-09-14 17:19 ` Eric W. Biederman
2010-09-14 17:46 ` Florian Mickler
2010-09-15 3:28 ` Joe Perches
2010-09-15 4:34 ` Florian Mickler
2010-09-15 4:45 ` Joe Perches
2010-09-15 12:49 ` Florian Mickler
2010-09-14 23:15 ` Joe Perches
2010-09-13 9:01 ` Florian Mickler
2010-09-14 17:24 ` Eric W. Biederman
2010-09-26 18:52 ` RFC: " Joe Perches
2010-09-27 14:57 ` Florian Mickler
2010-09-27 15:44 ` Ted Ts'o
2010-09-27 17:00 ` Florian Mickler
2010-09-27 18:21 ` Ted Ts'o
2010-09-27 19:26 ` Florian Mickler
2010-09-27 20:08 ` Joe Perches
2010-09-27 20:47 ` Ted Ts'o [this message]
2010-09-27 21:16 ` Joe Perches
2010-09-28 4:22 ` Ted Ts'o
2010-09-28 4:37 ` Mark Brown
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=20100927204756.GC3168@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=florian@mickler.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=w.sang@pengutronix.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;
as well as URLs for NNTP newsgroup(s).