From: Steven Rostedt <rostedt@goodmis.org>
To: Glauber Costa <glommer@parallels.com>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Richard Cochran <richardcochran@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
ksummit-2012-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-2012-discuss] [ATTEND or not ATTEND] That's the question!
Date: Fri, 06 Jul 2012 08:42:55 -0400 [thread overview]
Message-ID: <1341578575.14828.6.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4FF6C148.7030402@parallels.com>
On Fri, 2012-07-06 at 14:43 +0400, Glauber Costa wrote:
> > Please no!
> > I don't see why we should clutter the changelog with tags for reasons as
> > unimportant as measuring some patch's value!
> >
> Stronger: Having the maintainer to do more work is hardly a way to decrease
> the amount of work he does. (Well, it could be in some cases, but not in
> this)
Strongest: We actually implemented this. It was called 'Impact' tags
(search the git logs). Linus *hated* them. He got really upset and
flamed us for doing it.
https://lkml.org/lkml/2009/4/15/296
Basically it's duplicating the subject line. The subject line should
have the impact (worth) of the patch. Heck, we should just add
'/trivial' to the subject. Like "x86/trivial: clean white space in x.c".
Or /doc or /comment or whatever. That should not be a problem, searches
are nicer on git log --pretty=oneline, and we should push to have all
non functional changes have such a tag in the subject. Then we can split
these changes out from functional changes.
There, solved ;)
-- Steve
next prev parent reply other threads:[~2012-07-06 12:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 22:56 Thomas Gleixner
2012-06-15 23:34 ` [Ksummit-2012-discuss] " Greg KH
2012-06-16 10:50 ` Thomas Gleixner
2012-06-16 13:29 ` Jonathan Corbet
2012-06-16 13:32 ` Frederic Weisbecker
2012-06-16 13:56 ` Rafael J. Wysocki
2012-06-17 10:40 ` Thomas Gleixner
2012-06-17 18:51 ` Greg KH
2012-06-17 18:58 ` Mark Brown
2012-06-20 19:51 ` J. Bruce Fields
2012-07-06 9:43 ` Glauber Costa
2012-07-06 9:54 ` Frederic Weisbecker
2012-07-06 9:59 ` Glauber Costa
2012-07-06 10:00 ` Srivatsa S. Bhat
2012-07-06 10:03 ` Glauber Costa
2012-07-06 10:21 ` Srivatsa S. Bhat
2012-07-06 10:11 ` Richard Cochran
2012-07-06 10:14 ` Glauber Costa
2012-07-06 10:36 ` Srivatsa S. Bhat
2012-07-06 10:43 ` Glauber Costa
2012-07-06 12:42 ` Steven Rostedt [this message]
2012-07-17 22:17 ` david
2012-06-16 11:30 ` Alan Cox
2012-06-16 15:03 ` Phil Turmel
2012-06-16 16:43 ` Myklebust, Trond
2012-06-20 0:40 ` Dave Chinner
2012-06-17 17:04 ` Mark Brown
2012-06-19 15:45 ` Bjorn Helgaas
2012-06-19 19:18 ` Roland Dreier
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=1341578575.14828.6.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=glommer@parallels.com \
--cc=ksummit-2012-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®