From: Jeff King Date: Sun, 09 Jun 2013 05:36:21 GMT Subject: Re: [PATCH 2/2] git.txt: document GIT_TRACE_PACKET Message-ID: <20130609053621.GA1854@sigill.intra.peff.net> In-Reply-To: <1370755369-30868-2-git-send-email-pclouds@gmail.com> On Sun, Jun 09, 2013 at 12:22:49PM +0700, Nguyen Thai Ngoc Duy wrote: > diff --git a/Documentation/git.txt b/Documentation/git.txt > index c760918..72e9045 100644 > --- a/Documentation/git.txt > +++ b/Documentation/git.txt > @@ -845,6 +845,11 @@ for further details. > recorded. This may be helpful for troubleshooting some > pack-related performance problems. > > +'GIT_TRACE_PACKET':: > + If this variable is set, it shows a trace of all packets > + coming in or out of a given program. This can help with > + debugging object negotiation or other protocol issues. This is not quite true. It stops showing packets after it sees a packet starting with "PACK" (optionally with a sideband prefix). So you would miss, for example, a sideband error that came after the pack had started. So it is really only useful for looking at the ref and object negotiation phases. I know that probably sounds a bit nit-picky, but it might be worth making the distinction in case somebody is trying to track down such messages. -Peff