From: "tenglong.tl" <dyroneteng@gmail.com>
To: dyroneteng@gmail.com
Cc: avarab@gmail.com, git@jeffhostetler.com, git@vger.kernel.org,
gitster@pobox.com, tenglong.tl@alibaba-inc.com
Subject: [PATCH v1 0/2] tr2: shows the scope unconditionally with config
Date: Fri, 22 Jul 2022 16:19:30 +0800 [thread overview]
Message-ID: <cover.1658472474.git.dyroneteng@gmail.com> (raw)
In-Reply-To: <20220721132748.37848-1-tenglong.tl@alibaba-inc.com>
From: Teng Long <dyroneteng@gmail.com>
Changes since the initial patch:
1. [1/2] optimize the "scope" field representation with real syntax and
concrete value.
Thanks.
Teng Long (2):
api-trace2.txt: print config key-value pair
tr2: shows scope unconditionally in addition to key-value pair
Documentation/technical/api-trace2.txt | 41 ++++++++++++++++++++++++++
trace2/tr2_tgt_event.c | 3 ++
trace2/tr2_tgt_normal.c | 5 +++-
trace2/tr2_tgt_perf.c | 9 ++++--
4 files changed, 55 insertions(+), 3 deletions(-)
Range-diff against v0:
1: bebd97c832 ! 1: 32f8b9ae6b api-trace2.txt: print config key-value pair
@@ Commit message
Signed-off-by: Teng Long <dyroneteng@gmail.com>
## Documentation/technical/api-trace2.txt ##
+@@ Documentation/technical/api-trace2.txt: The "exec_id" field is a command-unique id and is only useful if the
+ {
+ "event":"def_param",
+ ...
++ "scope":"global",
+ "param":"core.abbrev",
+ "value":"7"
+ }
@@ Documentation/technical/api-trace2.txt: at offset 508.
This example also shows that thread names are assigned in a racy manner
as each thread starts and allocates TLS storage.
2: 2f8fce6599 ! 2: 78575cca0b tr2: shows scope unconditionally in addition to key-value pair
@@ Commit message
Signed-off-by: Teng Long <dyroneteng@gmail.com>
## Documentation/technical/api-trace2.txt ##
-@@ Documentation/technical/api-trace2.txt: The "exec_id" field is a command-unique id and is only useful if the
- {
- "event":"def_param",
- ...
-+ scope: <a string that 'git config --show-scope' would return>
- "param":"core.abbrev",
- "value":"7"
- }
@@ Documentation/technical/api-trace2.txt: Print Configs::
+
The environment variable `GIT_TRACE2_CONFIG_PARAMS` and configuration
--
2.37.1.1.g8cbb44ffc4.dirty
next prev parent reply other threads:[~2022-07-22 8:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:27 [PATCH 0/2] tr2: shows the scope unconditionally with config tenglong.tl
2022-07-21 13:27 ` [PATCH 1/2] api-trace2.txt: print config key-value pair tenglong.tl
2022-07-21 13:27 ` [PATCH 2/2] tr2: shows scope unconditionally in addition to " tenglong.tl
2022-07-21 16:57 ` Junio C Hamano
2022-07-22 6:12 ` tenglong.tl
2022-07-22 8:19 ` tenglong.tl [this message]
2022-07-22 8:19 ` [PATCH v1 1/2] api-trace2.txt: print config " tenglong.tl
2022-07-22 10:59 ` Ævar Arnfjörð Bjarmason
2022-07-25 19:07 ` Junio C Hamano
2022-08-01 12:25 ` tenglong.tl
2022-08-05 22:21 ` Junio C Hamano
2022-08-08 6:16 ` Teng Long
2022-07-22 21:05 ` Junio C Hamano
2022-07-23 6:06 ` tenglong.tl
2022-07-23 17:47 ` Junio C Hamano
2022-07-25 9:18 ` tenglong.tl
2022-07-22 8:19 ` [PATCH v1 2/2] tr2: shows scope unconditionally in addition to " tenglong.tl
2022-08-12 2:56 ` [PATCH v2 0/2] tr2: shows the scope unconditionally with config Teng Long
2022-08-12 2:56 ` [PATCH v2 1/2] api-trace2.txt: print config key-value pair Teng Long
2022-08-12 2:56 ` [PATCH v2 2/2] tr2: shows scope unconditionally in addition to " Teng Long
2022-08-12 21:16 ` Junio C Hamano
2022-08-19 21:18 ` [PATCH v2 0/2] tr2: shows the scope unconditionally with config 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=cover.1658472474.git.dyroneteng@gmail.com \
--to=dyroneteng@gmail.com \
--cc=avarab@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tenglong.tl@alibaba-inc.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.
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).