From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@amd64.org>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH] perf: Let O= makes handle relative paths
Date: Wed, 15 Aug 2012 16:38:05 +0200 [thread overview]
Message-ID: <1345041485.31459.89.camel@twins> (raw)
In-Reply-To: <20120815131806.GC4640@aftab.osrc.amd.com>
On Wed, 2012-08-15 at 15:18 +0200, Borislav Petkov wrote:
> On Wed, Aug 15, 2012 at 10:06:34AM -0300, Arnaldo Carvalho de Melo wrote:
> > That was the case in the past, but IIRC PeterZ advocated not to and I
> > agreed.
>
> Maybe you guys need to explain yourselves :) I mean, the dir is not
> present so we're not overwriting anything. And since we say "O=..." on
> the command line, it is actually expected that we really mean it... why
> type it, otherwise?
Because you're an idiot and made a typo ;-) Happens to me all the time.
The regular kernel build doesn't create non-existent O= targets either
iirc.
next prev parent reply other threads:[~2012-08-15 14:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 13:20 [PATCH] perf: Let O= makes handle relative paths Steven Rostedt
2012-08-13 13:24 ` Borislav Petkov
2012-08-13 14:23 ` Steven Rostedt
2012-08-13 14:29 ` Borislav Petkov
2012-08-13 18:02 ` Arnaldo Carvalho de Melo
2012-08-15 10:27 ` Borislav Petkov
2012-08-15 13:06 ` Arnaldo Carvalho de Melo
2012-08-15 13:18 ` Borislav Petkov
2012-08-15 14:38 ` Peter Zijlstra [this message]
2012-08-15 14:42 ` Borislav Petkov
2012-08-15 14:59 ` Arnaldo Carvalho de Melo
2012-08-15 16:39 ` Borislav Petkov
2012-08-16 16:07 ` Steven Rostedt
2012-08-16 17:12 ` Arnaldo Carvalho de Melo
2012-08-21 16:20 ` [tip:perf/core] perf tools: " tip-bot for 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=1345041485.31459.89.camel@twins \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.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