From: Josh Steadmon <steadmon@google.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, git@jeffhostetler.com
Subject: Re: [PATCH 0/2] Randomize / timestamp trace2 targets
Date: Fri, 15 Mar 2019 13:37:04 -0700 [thread overview]
Message-ID: <20190315203704.GC47591@google.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1903141531160.41@tvgsbejvaqbjf.bet>
On 2019.03.14 15:34, Johannes Schindelin wrote:
> Hi Josh,
>
> On Wed, 13 Mar 2019, Josh Steadmon wrote:
>
> > 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?
For my specific use case, getnanotime() would probably be sufficient.
However, others requested the timestamp feature before I sent this to
the list. I don't know whether they had a specific use case in mind.
next prev parent reply other threads:[~2019-03-15 20:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 23:33 [PATCH 0/2] Randomize / timestamp trace2 targets Josh Steadmon
2019-03-13 23:33 ` [PATCH 1/2] date: make get_time() public Josh Steadmon
2019-03-13 23:33 ` [PATCH 2/2] trace2: randomize/timestamp trace2 targets Josh Steadmon
2019-03-13 23:49 ` Ævar Arnfjörð Bjarmason
2019-03-15 18:39 ` Jeff Hostetler
2019-03-15 19:26 ` Ævar Arnfjörð Bjarmason
2019-03-15 20:14 ` Jeff Hostetler
2019-03-15 20:43 ` Josh Steadmon
2019-03-15 20:49 ` Josh Steadmon
2019-03-18 1:40 ` Junio C Hamano
2019-03-19 3:17 ` Jeff King
2019-03-14 0:16 ` Jeff King
2019-03-14 6:07 ` Junio C Hamano
2019-03-14 14:34 ` [PATCH 0/2] Randomize / timestamp " Johannes Schindelin
2019-03-15 20:37 ` Josh Steadmon [this message]
2019-03-15 19:18 ` Jeff Hostetler
2019-03-15 20:38 ` Josh Steadmon
2019-03-18 12:50 ` Jeff Hostetler
2019-03-21 0:16 ` [PATCH v2 0/1] Write trace2 output to directories Josh Steadmon
2019-03-21 0:16 ` [PATCH v2 1/1] trace2: write to directory targets Josh Steadmon
2019-03-21 2:04 ` Junio C Hamano
2019-03-21 17:43 ` Jeff Hostetler
2019-03-22 3:30 ` Junio C Hamano
2019-03-22 14:20 ` Jeff Hostetler
2019-03-21 21:09 ` [PATCH v3 0/1] Write trace2 output to directories Josh Steadmon
2019-03-21 21:09 ` [PATCH v3 1/1] trace2: write to directory targets Josh Steadmon
2019-03-23 20:44 ` Ævar Arnfjörð Bjarmason
2019-03-24 12:33 ` Junio C Hamano
2019-03-24 14:51 ` Ævar Arnfjörð Bjarmason
2019-03-25 2:21 ` Junio C Hamano
2019-03-25 8:21 ` Ævar Arnfjörð Bjarmason
2019-03-25 16:29 ` Jeff Hostetler
2019-03-21 21:16 ` [PATCH v3 0/1] Write trace2 output to directories Jeff Hostetler
2019-03-22 5:23 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190315203704.GC47591@google.com \
--to=steadmon@google.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).