Re: [PATCH 0/2] Randomize / timestamp trace2 targets

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 14, 2019, 14:34 UTC
Message-ID: <nycvar.QRO.7.76.6.1903141531160.41@tvgsbejvaqbjf.bet>
In-Reply-To: <cover.1552519463.git.steadmon@google.com>

Hi Josh,

On Wed, 13 Mar 2019, Josh Steadmon wrote:

Show 5 quoted lines

> Persistently enabling trace2 output is difficult because it requires
> specifying a full filename. This series teaches tr2_dst_get_trace_fd()
> to randomize filenames when a directory or filename prefix are given as
> targets in the GIT_TR2_* envvars. It also allows expansion of a
> timestamp template string into the current UTC timestamp.

Given the problem you try to solve, would it not make more sense to use `getnanotime()` than some randomized file name or an ISO date format?

Ciao, Johannes

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.