All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Paul Mackerras <paulus@samba.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH] perf tools: Fixup for removing -f option in perf record
Date: Thu, 27 Jun 2013 12:47:50 +0200	[thread overview]
Message-ID: <20130627104750.GB27378@dyad.programming.kicks-ass.net> (raw)
In-Reply-To: <20130627103931.GA5534@gmail.com>

On Thu, Jun 27, 2013 at 12:39:31PM +0200, Ingo Molnar wrote:
> 
> * Peter Zijlstra <peterz@infradead.org> wrote:
> 
> > On Thu, Jun 27, 2013 at 01:25:20PM +0900, Namhyung Kim wrote:
> > > From: Namhyung Kim <namhyung.kim@lge.com>
> > > 
> > > The commit bf3da4014a0c ("perf record: Remove -f/--force option") got
> > > rid of -f option from perf record.  But this option was used
> > > internally by various sub-commands so they wouldn't work anymore.
> > > Also update the example document not to use -f option.
> > 
> > Oh man.. we got rid of -f? Do we now default to over-write existing data
> > file?
> 
> I thought -f was the implied default for ages?

OK.. I've been dutifully typing it all this while :-)

  reply	other threads:[~2013-06-27 10:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27  4:25 [PATCH] perf tools: Fixup for removing -f option in perf record Namhyung Kim
2013-06-27  9:36 ` Peter Zijlstra
2013-06-27 10:39   ` Ingo Molnar
2013-06-27 10:47     ` Peter Zijlstra [this message]
2013-06-28  9:47       ` Jiri Olsa
2013-06-28 14:17         ` David Ahern
2013-06-28 15:37           ` Ingo Molnar
2013-06-28 16:03             ` David Ahern
2013-06-28 16:07               ` Ingo Molnar
2013-07-09  7:41 ` Namhyung Kim
2013-07-09 14:21   ` David Ahern
2013-07-10  0:07     ` Namhyung Kim
2013-07-12  8:50 ` [tip:perf/urgent] perf record: Remove -f/--force option tip-bot for Jiri Olsa

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=20130627104750.GB27378@dyad.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@ghostprotocols.net \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.