perf tools: gitignore *.data
PATCH 1/1 perf tools: gitignore *.data
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.
--- tools/perf/.gitignore | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
tools/perf/.gitignore +1 -0
@@ -14,3 +14,4 @@ common-cmds.h tags TAGS cscope* +*.data
Signature · 1 line
1.6.2.5
Quoted 7 lines · Jaswinder Singh Rajput
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
Quoted 14 lines · Ingo Molnar
Quoted 7 lines · Jaswinder Singh Rajput
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*
+*.dataok, this is something i wanted to revisit eventually - the 'perf.data' name sucks a bit - as .data postfix is quite unspecific.
Quoted 8 lines
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).
Quoted 18 lines · Frederic Weisbecker
Quoted 17 lines · Ingo Molnar
Quoted 7 lines · Jaswinder Singh Rajput
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*
+*.dataok, 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?
Quoted 7 lines
Quoted 5 lines
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:
Quoted 25 lines · Frederic Weisbecker
Quoted 23 lines · Ingo Molnar
Quoted 21 lines · Jaswinder Singh Rajput
Quoted 8 lines
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*
+*.dataok, 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?
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
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