From: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: szeder.dev@gmail.com, git@jeffhostetler.com,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] trace2: Add variable description to git.txt
Date: Fri, 10 May 2019 12:44:24 -0700 (PDT) [thread overview]
Message-ID: <pull.189.git.gitgitgadget@gmail.com> (raw)
Jeff is out this week, so I picked up this request from Szeder. I'm very
open to edit suggestions.
Thanks, -Stolee
In-Reply-To: 20190510172824.GR14763@szeder.dev
Derrick Stolee (1):
trace2: Add variable description to git.txt
Documentation/git.txt | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
base-commit: c173542c84cdf5e71b393e91f9d9664a85f995b2
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-189%2Fderrickstolee%2Ftrace2-docs-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-189/derrickstolee/trace2-docs-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/189
--
gitgitgadget
next reply other threads:[~2019-05-10 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 19:44 Derrick Stolee via GitGitGadget [this message]
2019-05-10 19:44 ` [PATCH 1/1] trace2: Add variable description to git.txt Derrick Stolee via GitGitGadget
2019-05-10 21:15 ` SZEDER Gábor
2019-05-19 14:43 ` [PATCH 1/2] trace2: rename environment variables to GIT_TRACE2* SZEDER Gábor
2019-05-19 14:43 ` [PATCH 2/2] trace2: document the supported values of GIT_TRACE2* env variables SZEDER Gábor
2019-05-28 16:25 ` [PATCH 1/2] trace2: rename environment variables to GIT_TRACE2* Junio C Hamano
2019-05-28 16:46 ` Derrick Stolee
2019-05-29 19:52 ` Jeff Hostetler
2019-05-28 23:02 ` Ævar Arnfjörð Bjarmason
2019-05-29 19:58 ` Jeff Hostetler
2019-05-29 21:45 ` Junio C Hamano
2019-06-12 14:29 ` [PATCH] Revert "test-lib: whitelist GIT_TR2_* in the environment" Ævar Arnfjörð Bjarmason
2019-06-12 17:49 ` 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=pull.189.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@gmail.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).