[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPh34mdr=AVoPBprcgt+dPW8yzGzTf5K838dz3caiSAPry8D7w@mail.gmail.com>
Date: Mon, 10 Nov 2014 14:37:16 +0100
From: Hagen Paul Pfeifer <hagen@...u.net>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Hemant Kumar <hemant@...ux.vnet.ibm.com>,
Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
srikar@...ux.vnet.ibm.com, oleg@...hat.com,
hegdevasant@...ux.vnet.ibm.com, mingo@...hat.com,
systemtap@...rceware.org, aravinda@...ux.vnet.ibm.com,
penberg@....fi, brendan.d.gregg@...il.com,
"yrl.pp-manager.tt@...achi.com" <yrl.pp-manager.tt@...achi.com>
Subject: Re: [RFC] perf-cache command interface design
On 10 November 2014 13:50, Peter Zijlstra <peterz@...radead.org> wrote:
> # env | grep XDG | wc -l
> 0
>
> Which renders it useless crap in my book.
>
> I agree on the .debug name being somewhat generic, also, it would be:
> man 8 file-hierarchy, but that too fails:
>
> $ man file-hierarchy
> No manual entry for file-hierarchy
Ok, but then we are not even consistent to ourself, see "perf: Add
support for full Intel event lists" which download already to
$XDG_CACHE_HOME [1]. It is not useless to agree on one standard.
Reinvent the place where caches and configurations are stored again
and again is somewhat stupid. E.g. ~/.cache (or $XDG_CACHE_HOME) can
be deleted without problems, ~/.config not, and so on. Someone
(Rusty?) thought about this several years ago, IMHO we should give at
least a try.
Hagen
[1] https://lkml.org/lkml/2014/7/30/686
--
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/
Powered by blists - more mailing lists