From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Robert Richter <robert.richter@amd.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Anton Blanchard <anton@samba.org>,
Sam Ravnborg <sam@ravnborg.org>,
Peter Zijlstra <peterz@infradead.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] perf tools: gitignore *.data
Date: Fri, 3 Jul 2009 15:09:39 +0200 [thread overview]
Message-ID: <20090703130936.GA5072@nowhere> (raw)
In-Reply-To: <20090703103852.GA3242@elte.hu>
On Fri, Jul 03, 2009 at 12:38:52PM +0200, Ingo Molnar wrote:
>
> * Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
>
> > perf.data made by perf record is a data file and need to be
> > ignored by git
> >
> > Added *.data so that perf.data and its friends will be ignored.
>
> > cscope*
> > +*.data
>
> ok, this is something i wanted to revisit eventually - the
> 'perf.data' name sucks a bit - as .data postfix is quite unspecific.
>
> Perhaps trace.perf is a better default name, and all files would
> have the .perf postfix?
>
> I've Cc:-ed a number of folks who might have an opinion about this -
> what would be the best default naming and postfix for perf binary
> files?
>
> Ingo
perf.bin seems to me adequate as it tells everything (IMHO).
next prev parent reply other threads:[~2009-07-03 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 6:39 [PATCH -tip] perf tools: gitignore *.data Jaswinder Singh Rajput
2009-07-03 10:38 ` Ingo Molnar
2009-07-03 13:09 ` Frederic Weisbecker [this message]
2009-07-03 13:18 ` Ingo Molnar
2009-07-03 14:36 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2009-07-03 6:32 Jaswinder Singh Rajput
2009-07-03 6:40 ` Jaswinder Singh Rajput
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=20090703130936.GA5072@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=anton@samba.org \
--cc=efault@gmx.de \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.