From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Robert Richter" <robert.richter@amd.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: [PATCH] ring_buffer: fix ring_buffer_event_length()
Date: Thu, 8 Jan 2009 15:40:46 +0100 [thread overview]
Message-ID: <20090108144046.GB18120@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0901080927340.22642@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Thu, 8 Jan 2009, Ingo Molnar wrote:
> >
> > That is a pretty useless duplication of the subject line, so i dropped it.
> > When the subject line explains the practical impact already, there's no
> > need to add the impact line.
>
> Actually, Frederic and I had a discussion about a duplicate Impact line.
> Perhaps someone is searching the git log on "Impact:" looking for all
> fixes. Perhaps just a simple:
>
> Impact: fix
>
> would be sufficient?
hm, okay - but it should be somewhat different. The impact line should
really be a 'description of impact/risk'. That overlaps subject lines some
of the time - but often not. So we could do something more specific like:
Impact: change/fix (unused) ring-buffer API to be more useful
(For future commits.)
Ingo
prev parent reply other threads:[~2009-01-08 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 4:58 Steven Rostedt
2009-01-08 5:29 ` Andrew Morton
2009-01-08 11:55 ` Ingo Molnar
2009-01-08 19:26 ` Andrew Morton
2009-01-11 3:44 ` Ingo Molnar
2009-01-08 14:18 ` Steven Rostedt
2009-01-08 14:46 ` Ingo Molnar
2009-01-08 11:59 ` Ingo Molnar
2009-01-08 14:28 ` Steven Rostedt
2009-01-08 14:40 ` Ingo Molnar [this message]
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=20090108144046.GB18120@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.richter@amd.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®