From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>,
Alexander Viro <viro@ftp.linux.org.uk>
Cc: tytso@mit.edu, Alex Buell <alex.buell@munted.org.uk>,
Mailing Lists - Kernel Developers <linux-kernel@vger.kernel.org>,
Eric Paris <eparis@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: Article in Phoronix about loss of performance in 2.6.35 release candidates
Date: Tue, 1 Jun 2010 08:25:40 +0200 [thread overview]
Message-ID: <20100601062540.GA31131@elte.hu> (raw)
In-Reply-To: <20100601061749.GA26705@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> Is lacking pretty much all essential pieces of information which are
> required for reverts:
>
> - it has no description about who reported the bug.
In fact it was _bisected_ by Eric Paris, so a Bisected-by tag is a must.
Eric is a nice guy and i'm sure wont complain about this, but i can tell it
with a 100% certainty that to most testers and developers bisecting bugs is a
tiresome and error-prone process that involves quite a bit of work.
Bisecting a bug is often more work to do than the work which went into the
original commit and the revert, combined.
So if we want more people to test our commits then the least we can do is to
credit testers by making proper use of the Reported-by and Bisected-by tags.
Ingo
next prev parent reply other threads:[~2010-06-01 6:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 23:19 Article in Phoronix about loss of performance in 2.6.35 release candidates Alex Buell
2010-05-31 23:39 ` Robert Hancock
2010-06-01 0:46 ` Alex Buell
2010-06-01 0:52 ` Dave Airlie
2010-06-01 3:15 ` Bill Davidsen
2010-06-01 3:22 ` Robert Hancock
2010-06-01 5:38 ` Mike Galbraith
2010-06-01 4:10 ` tytso
2010-06-01 5:00 ` Pekka Enberg
2010-06-01 6:17 ` Ingo Molnar
2010-06-01 6:25 ` Ingo Molnar [this message]
2010-06-01 6:53 ` Ingo Molnar
2010-06-01 12:44 ` Chris Mason
2010-06-01 6:35 ` Ingo Molnar
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=20100601062540.GA31131@elte.hu \
--to=mingo@elte.hu \
--cc=alex.buell@munted.org.uk \
--cc=arjan@infradead.org \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@ftp.linux.org.uk \
/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