From: Elia Pinto <gitter.spiros@gmail•com>
To: git@vger•kernel.org
Cc: tboegi@web•de, ramsay@ramsayjones•plus.com, gitster@pobox•com,
sunshine@sunshineco•com, peff@peff•net,
Elia Pinto <gitter.spiros@gmail•com>
Subject: [PATCHv3 1/3] git.txt: document the new GIT_TRACE_CURL environment variable
Date: Wed, 20 Apr 2016 16:28:23 +0000 [thread overview]
Message-ID: <20160420162825.62380-2-gitter.spiros@gmail.com> (raw)
In-Reply-To: <20160420162825.62380-1-gitter.spiros@gmail.com>
Describe the purpose of the GIT_TRACE_CURL environment variable.
Helped-by: Torsten Bögershausen <tboegi@web•de>
Helped-by: Ramsay Jones <ramsay@ramsayjones•plus.com>
Helped-by: Junio C Hamano <gitster@pobox•com>
Helped-by: Eric Sunshine <sunshine@sunshineco•com>
Helped-by: Jeff King <peff@peff•net>
Signed-off-by: Elia Pinto <gitter.spiros@gmail•com>
---
Documentation/git.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 8afe349..958db0f 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -1075,6 +1075,14 @@ of clones and fetches.
cloning of shallow repositories.
See 'GIT_TRACE' for available trace output options.
+'GIT_TRACE_CURL'::
+ Enables a curl full trace dump of all incoming and outgoing data,
+ including descriptive information, of the git transport protocol.
+ This is similar to doing curl --trace-ascii on the command line.
+ This option overrides setting the GIT_CURL_VERBOSE environment
+ variable.
+ See 'GIT_TRACE' for available trace output options.
+
'GIT_LITERAL_PATHSPECS'::
Setting this variable to `1` will cause Git to treat all
pathspecs literally, rather than as glob patterns. For example,
--
2.8.1.383.g31b84cc
next prev parent reply other threads:[~2016-04-20 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 16:28 [PATCHv3 0/3] Implements the GIT_TRACE_CURL environment variable Elia Pinto
2016-04-20 16:28 ` Elia Pinto [this message]
2016-04-20 16:28 ` [PATCHv3 2/3] imap-send.c: introduce the GIT_TRACE_CURL enviroment variable Elia Pinto
2016-04-20 16:28 ` [PATCHv3 3/3] http.c: implements the GIT_TRACE_CURL environment variable Elia Pinto
2016-04-20 18:53 ` Junio C Hamano
2016-04-20 19:56 ` Ramsay Jones
2016-04-20 20:07 ` Junio C Hamano
2016-04-20 18:41 ` [PATCHv3 0/3] Implements " Junio C Hamano
2016-04-20 19:49 ` Ramsay Jones
2016-04-20 20:45 ` Jeff King
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=20160420162825.62380-2-gitter.spiros@gmail.com \
--to=gitter.spiros@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=ramsay@ramsayjones$(echo .)plus.com \
--cc=sunshine@sunshineco$(echo .)com \
--cc=tboegi@web$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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