From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
lihong.hi@gmail.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: + recordmcount-stfu.patch added to -mm tree
Date: Sun, 15 Nov 2009 09:17:36 +0100 [thread overview]
Message-ID: <20091115081736.GA29826@elte.hu> (raw)
In-Reply-To: <1258231467.22249.438.camel@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sat, 2009-11-14 at 10:27 +0100, Ingo Molnar wrote:
> > * Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > > On Fri, 2009-11-13 at 21:26 -0800, Andrew Morton wrote:
> > >
> > > > Dunno, really. How many people are running old objdump, and do we
> > > > want to retard the rate at which the stragglers will upgrade?
> > >
> > > I guess not, but by printing out a warning
> > > 1000000000000000000000000000 times per build, it may encourage them to
> > > upgrade ;-)
> >
> > If that binutils version is still supported this is not the right
> > method. People are in their full rights to be at any version within the
> > supported versions interval, and we should not 'force' them.
>
> It's not forcing them. [...]
My point was that by printing a warning 1000000000000000000000000000
times per build we effectively force them, by making life unpleasant.
Ingo
next prev parent reply other threads:[~2009-11-15 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200911140356.nAE3utfU001939@imap1.linux-foundation.org>
2009-11-14 4:58 ` + recordmcount-stfu.patch added to -mm tree Steven Rostedt
2009-11-14 5:26 ` Andrew Morton
2009-11-14 5:33 ` Steven Rostedt
2009-11-14 9:27 ` Ingo Molnar
2009-11-14 20:44 ` Steven Rostedt
2009-11-15 8:17 ` Ingo Molnar [this message]
2009-11-15 15:25 ` Steven Rostedt
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=20091115081736.GA29826@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=lihong.hi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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