From: Junio C Hamano <gitster@pobox.com>
To: Josh Steadmon <steadmon@google.com>,
Jeff Hostetler <jeffhost@microsoft.com>
Cc: git@vger.kernel.org, git@jeffhostetler.com
Subject: Re: [PATCH] trace2: increment event format version
Date: Thu, 11 Nov 2021 15:03:10 -0800 [thread overview]
Message-ID: <xmqqh7cijnwx.fsf@gitster.g> (raw)
In-Reply-To: <ebc4d9a6960f0350772c14981ef211876f29d0fa.1636669891.git.steadmon@google.com> (Josh Steadmon's message of "Thu, 11 Nov 2021 14:34:25 -0800")
Josh Steadmon <steadmon@google.com> writes:
> In 64bc752 (trace2: add trace2_child_ready() to report on background
> children, 2021-09-20), we added a new "child_ready" event. In
> Documentation/technical/api-trace2.txt, we promise that adding a new
> event type will result in incrementing the trace2 event format version
> number, but this was not done. Correct this in code & docs.
>
> Signed-off-by: Josh Steadmon <steadmon@google.com>
> ---
> Documentation/technical/api-trace2.txt | 4 ++--
> trace2/tr2_tgt_event.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Hmph, it seems to me that this is better done before the release,
or am I mistaken?
>
> diff --git a/Documentation/technical/api-trace2.txt b/Documentation/technical/api-trace2.txt
> index ef7fe02a8f..bb13ca3db8 100644
> --- a/Documentation/technical/api-trace2.txt
> +++ b/Documentation/technical/api-trace2.txt
> @@ -128,7 +128,7 @@ yields
>
> ------------
> $ cat ~/log.event
> -{"event":"version","sid":"sid":"20190408T191610.507018Z-H9b68c35f-P000059a8","thread":"main","time":"2019-01-16T17:28:42.620713Z","file":"common-main.c","line":38,"evt":"2","exe":"2.20.1.155.g426c96fcdb"}
> +{"event":"version","sid":"sid":"20190408T191610.507018Z-H9b68c35f-P000059a8","thread":"main","time":"2019-01-16T17:28:42.620713Z","file":"common-main.c","line":38,"evt":"3","exe":"2.20.1.155.g426c96fcdb"}
> {"event":"start","sid":"20190408T191610.507018Z-H9b68c35f-P000059a8","thread":"main","time":"2019-01-16T17:28:42.621027Z","file":"common-main.c","line":39,"t_abs":0.001173,"argv":["git","version"]}
> {"event":"cmd_name","sid":"20190408T191610.507018Z-H9b68c35f-P000059a8","thread":"main","time":"2019-01-16T17:28:42.621122Z","file":"git.c","line":432,"name":"version","hierarchy":"version"}
> {"event":"exit","sid":"20190408T191610.507018Z-H9b68c35f-P000059a8","thread":"main","time":"2019-01-16T17:28:42.621236Z","file":"git.c","line":662,"t_abs":0.001227,"code":0}
> @@ -391,7 +391,7 @@ only present on the "start" and "atexit" events.
> {
> "event":"version",
> ...
> - "evt":"2", # EVENT format version
> + "evt":"3", # EVENT format version
> "exe":"2.20.1.155.g426c96fcdb" # git version
> }
> ------------
> diff --git a/trace2/tr2_tgt_event.c b/trace2/tr2_tgt_event.c
> index 70cfc2f77c..3a0014417c 100644
> --- a/trace2/tr2_tgt_event.c
> +++ b/trace2/tr2_tgt_event.c
> @@ -20,7 +20,7 @@ static struct tr2_dst tr2dst_event = { TR2_SYSENV_EVENT, 0, 0, 0, 0 };
> * a new field to an existing event, do not require an increment to the EVENT
> * format version.
> */
> -#define TR2_EVENT_VERSION "2"
> +#define TR2_EVENT_VERSION "3"
>
> /*
> * Region nesting limit for messages written to the event target.
>
> base-commit: e9e5ba39a78c8f5057262d49e261b42a8660d5b9
next prev parent reply other threads:[~2021-11-11 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 22:34 [PATCH] trace2: increment event format version Josh Steadmon
2021-11-11 23:03 ` Junio C Hamano [this message]
2021-11-11 23:06 ` Josh Steadmon
2021-11-11 23:47 ` Junio C Hamano
2021-11-12 22:33 ` Ævar Arnfjörð Bjarmason
2021-11-12 23:28 ` Junio C Hamano
2021-12-01 15:49 ` Jeff Hostetler
2021-12-01 15:57 ` Ævar Arnfjörð Bjarmason
2021-12-01 19:56 ` Josh Steadmon
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=xmqqh7cijnwx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=jeffhost@microsoft.com \
--cc=steadmon@google.com \
/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 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 NNTP newsgroup(s).