linux-kernel - Re: [PATCH -tip] perf tools: gitignore *.data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090703103852.GA3242@elte.hu>
Date:	Fri, 3 Jul 2009 12:38:52 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Robert Richter <robert.richter@....com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Anton Blanchard <anton@...ba.org>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	Peter Zijlstra <peterz@...radead.org>,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip] perf tools: gitignore *.data


* Jaswinder Singh Rajput <jaswinder@...nel.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/