From: Josh Steadmon <steadmon@google.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org, git@jeffhostetler.com
Subject: Re: [PATCH 2/2] trace2: randomize/timestamp trace2 targets
Date: Fri, 15 Mar 2019 13:49:19 -0700 [thread overview]
Message-ID: <20190315204919.GF47591@google.com> (raw)
In-Reply-To: <20190315204327.GE47591@google.com>
On 2019.03.15 13:43, Josh Steadmon wrote:
> On 2019.03.14 00:49, Ævar Arnfjörð Bjarmason wrote:
> >
> > On Thu, Mar 14 2019, Josh Steadmon wrote:
> >
> > > When the value of a trace2 environment variable contains instances of
> > > the string "%ISO8601%", expand them into the current UTC timestamp in
> > > ISO 8601 format.
> >
> > Any reason not to just support feeding the path to strbuf_addftime(), to
> > e.g. support a daily/hourly log?
>
> No reason not to. Seems reasonable to me.
Although as Junio says elsewhere in this thread, it's possible that we
may want to support fields other than timestamps.
next prev parent reply other threads:[~2019-03-15 20:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190315204919.GF47591@google.com \
--to=steadmon@google.com \
--cc=avarab@gmail.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.