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.
Signed-off-by: Jaswinder Singh Rajput <[email protected]>
---
tools/perf/.gitignore | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/tools/perf/.gitignore b/tools/perf/.gitignore
index d69a759..057deea 100644
--- a/tools/perf/.gitignore
+++ b/tools/perf/.gitignore
@@ -14,3 +14,4 @@ common-cmds.h
tags
TAGS
cscope*
+*.data
--
1.6.2.5
* Jaswinder Singh Rajput <[email protected]> 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
On Fri, Jul 03, 2009 at 12:38:52PM +0200, Ingo Molnar wrote:
>
> * Jaswinder Singh Rajput <[email protected]> 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).
* Frederic Weisbecker <[email protected]> wrote:
> On Fri, Jul 03, 2009 at 12:38:52PM +0200, Ingo Molnar wrote:
> >
> > * Jaswinder Singh Rajput <[email protected]> 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).
hm, .bin is pretty overloaded as well. It also suggests a
'executable binary' in a certain way - which it isnt.
Ingo
Em Fri, Jul 03, 2009 at 03:18:24PM +0200, Ingo Molnar escreveu:
>
> * Frederic Weisbecker <[email protected]> wrote:
>
> > On Fri, Jul 03, 2009 at 12:38:52PM +0200, Ingo Molnar wrote:
> > >
> > > * Jaswinder Singh Rajput <[email protected]> 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).
>
> hm, .bin is pretty overloaded as well. It also suggests a
> 'executable binary' in a certain way - which it isnt.
.samples
.perf
.perf_samples
.ps - oops, also used ;-)
- Arnaldo