From: Ben Peart <peartben@gmail.com>
To: Alex Vandiver <alexmv@dropbox.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/4] fsmonitor: Document GIT_TRACE_FSMONITOR
Date: Fri, 20 Oct 2017 09:19:04 -0400 [thread overview]
Message-ID: <2ef8f550-610e-6a9f-32e8-f2fe99b044ff@gmail.com> (raw)
In-Reply-To: <169bbc6117f518ffc9371fea7dfd11439105cc80.1508461850.git.alexmv@dropbox.com>
On 10/19/2017 9:11 PM, Alex Vandiver wrote:
> Signed-off-by: Alex Vandiver <alexmv@dropbox.com>
> ---
> Documentation/git.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/git.txt b/Documentation/git.txt
> index 1fca63634..720db196e 100644
> --- a/Documentation/git.txt
> +++ b/Documentation/git.txt
> @@ -594,6 +594,10 @@ into it.
> Unsetting the variable, or setting it to empty, "0" or
> "false" (case insensitive) disables trace messages.
>
> +`GIT_TRACE_FSMONITOR`::
> + Enables trace messages for the filesystem monitor extension.
> + See `GIT_TRACE` for available trace output options.
> +
> `GIT_TRACE_PACK_ACCESS`::
> Enables trace messages for all accesses to any packs. For each
> access, the pack file name and an offset in the pack is
>
Looks like a reasonable addition. Thank you.
next prev parent reply other threads:[~2017-10-20 13:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 1:11 [PATCH 0/4] fsmonitor fixes Alex Vandiver
2017-10-20 1:11 ` [PATCH 1/4] fsmonitor: Watch, and ask about, the top of the repo, not the CWD Alex Vandiver
2017-10-20 1:11 ` [PATCH 2/4] fsmonitor: Don't bother pretty-printing JSON from watchman Alex Vandiver
2017-10-20 13:00 ` Johannes Schindelin
2017-10-20 13:17 ` Ben Peart
2017-10-26 0:44 ` Alex Vandiver
2017-10-27 15:13 ` Johannes Schindelin
2017-10-20 1:11 ` [PATCH 3/4] fsmonitor: Document GIT_TRACE_FSMONITOR Alex Vandiver
2017-10-20 13:19 ` Ben Peart [this message]
2017-10-20 1:11 ` [PATCH 4/4] fsmonitor: Delay updating state until after split index is merged Alex Vandiver
2017-10-20 13:16 ` Johannes Schindelin
2017-10-20 21:47 ` Ben Peart
2017-10-21 2:06 ` Junio C Hamano
2017-10-21 3:35 ` Jeff King
2017-10-23 9:57 ` Johannes Schindelin
2017-10-23 12:36 ` Ben Peart
2017-10-26 1:20 ` Alex Vandiver
2017-10-20 12:58 ` [PATCH 1/4] fsmonitor: Watch, and ask about, the top of the repo, not the CWD Johannes Schindelin
2017-10-26 0:20 ` Alex Vandiver
2017-10-27 15:11 ` Johannes Schindelin
2017-10-20 13:17 ` [PATCH 0/4] fsmonitor fixes Johannes Schindelin
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=2ef8f550-610e-6a9f-32e8-f2fe99b044ff@gmail.com \
--to=peartben@gmail.com \
--cc=alexmv@dropbox.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 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).