From: Junio C Hamano <gitster@pobox.com>
To: Josh Steadmon <steadmon@google.com>
Cc: Jeff Hostetler <jeffhost@microsoft.com>,
git@vger.kernel.org, git@jeffhostetler.com
Subject: Re: [PATCH] trace2: increment event format version
Date: Thu, 11 Nov 2021 15:47:01 -0800 [thread overview]
Message-ID: <xmqqczn6jlvu.fsf@gitster.g> (raw)
In-Reply-To: <YY2h5lO90vo3Dy42@google.com> (Josh Steadmon's message of "Thu, 11 Nov 2021 15:06:14 -0800")
Josh Steadmon <steadmon@google.com> writes:
> On 2021.11.11 15:03, Junio C Hamano wrote:
>> 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?
>
> Ideally yes, although I am not sure if there is anyone using traces who
> strongly depends on the accuracy of the evt field.
Relieving us from having to keep track of the actual users is the
point of documenting to making promises ;-)
> For release-blocking
> fixes (for lack of a better term), should I have sent this patch
> differently?
I do not think so.
Thanks.
next prev parent reply other threads:[~2021-11-11 23:47 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
2021-11-11 23:06 ` Josh Steadmon
2021-11-11 23:47 ` Junio C Hamano [this message]
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=xmqqczn6jlvu.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 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.