From: Jeff King <peff@peff.net>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"Torsten Bögershausen" <tboegi@web.de>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)
Date: Thu, 16 Jun 2016 08:36:44 -0400 [thread overview]
Message-ID: <20160616123644.GD15988@sigill.intra.peff.net> (raw)
In-Reply-To: <CA+EOSBm5DLkv2RyovSrOuvqDS6OR15g5Z_JuGthwQr2t=R8vdg@mail.gmail.com>
On Wed, Jun 15, 2016 at 09:35:20AM +0200, Elia Pinto wrote:
> > * ep/http-curl-trace (2016-05-24) 2 commits
> > - imap-send.c: introduce the GIT_TRACE_CURL enviroment variable
> > - http.c: implement the GIT_TRACE_CURL environment variable
> >
> > HTTP transport gained an option to produce more detailed debugging
> > trace.
> >
> > Rerolled. Is everybody happy with this version?
> >
> The refs is there
> http://git.661346.n2.nabble.com/PATCH-v7-0-2-Implement-the-GIT-TRACE-CURL-environment-variable-td7657079.html
>
> If kindly someone who has reviewed and helped me to do the patch
> could give an ack (or a nack eventually). Thanks in advance
I gave another look at what is queued in pu, and I think it is OK. I
still find the output a little verbose, but I think we should ship it
and see how it fares in practice while debugging. I don't think its
exact format needs to be set in stone, so we can tweak it later if we
choose.
-Peff
PS Please trim your quotes to just the relevant bits.
next prev parent reply other threads:[~2016-06-16 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 22:08 What's cooking in git.git (Jun 2016, #04; Tue, 14) Junio C Hamano
2016-06-15 2:36 ` Mike Hommey
2016-06-15 18:32 ` Junio C Hamano
2016-06-16 4:16 ` Mike Hommey
2016-06-15 7:35 ` Elia Pinto
2016-06-16 12:36 ` Jeff King [this message]
2016-06-16 21:14 ` Junio C Hamano
2016-06-15 10:12 ` Duy Nguyen
2016-06-15 18:45 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160616123644.GD15988@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitter.spiros@gmail.com \
--cc=ramsay@ramsayjones.plus.com \
--cc=sunshine@sunshineco.com \
--cc=tboegi@web.de \
/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).