git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] git.txt: document GIT_TRACE_PACKET

From
Jeff King <peff@peff.net>
Date
Jun 9, 2013, 05:55 UTC
Message-ID
<20130609055509.GA17617@sigill.intra.peff.net>
In-Reply-To
<1370757210-2994-1-git-send-email-pclouds@gmail.com>
On Sun, Jun 09, 2013 at 12:53:30PM +0700, Nguyen Thai Ngoc Duy wrote:
Show 19 quoted lines
> "This can help with debugging object negotiation or other protocol
> issues."
> 
> Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
> ---
>  >> +'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 blindly copied the first paragraph from bbc30f9 (add packet tracing
>  debug code - 2011-02-24) and missed the "PACK" bit in the second one.
>  How about this?

Hmm, what do you know, I sort-of documented it already. I think I just never guessed that anybody but people reading "git log" would actually need to use TRACE_PACKET. :)

Thanks, the patch looks fine to me.
-Peff
Previous: Nguyễn Thái Ngọc DuyNext: Junio C Hamano
Message 5 of 9 in “core: use env variable instead of config var to turn on logging pack access”
  1. 1/2 core: use env variable instead of config var to turn on logging pack accessNguyễn Thái Ngọc Duy, Jun 9, 2013
  2. 2/2 git.txt: document GIT_TRACE_PACKETNguyễn Thái Ngọc Duy, Jun 9, 2013
  3. Jeff KingJun 9, 2013
  4. 2/2 git.txt: document GIT_TRACE_PACKETNguyễn Thái Ngọc Duy, Jun 9, 2013
  5. Jeff KingJun 9, 2013
  6. Junio C HamanoJun 9, 2013
  7. Eric SunshineJun 9, 2013
  8. Eric SunshineJun 9, 2013
  9. Eric SunshineJun 9, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.