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

Re: git-daemon shallow checkout fail

From
Bob Proulx <bob@proulx.com>
Date
Feb 7, 2017, 22:49 UTC
Message-ID
<20170207154512329677197@bob.proulx.com>
In-Reply-To
<CACsJy8D_X7u+kttu=ZD734u6nhR=wjMh0m99RBvm0_FOW74pWA@mail.gmail.com>
Duy Nguyen wrote:
Show 6 quoted lines
> I wonder if we should make this "git/1.9.1" information more visible. We could
> 
> 1) Always print it when cloning
> 2) Print it when cloning with -v (printing all capabilities with -v
> might not be a bad idea)
> 3) Include it in error messages when clone/fetch fails

I don't think I would want to see it all of the time. It isn't needed all of the time. But having it printable upon demand is nice. Being able to use GIT_TRACE_PACKET=1 worked very well. The only thing I needed was to know it was available so that I could use it. I am not sure where that is documented.

Therefore if and only if a change was made I would vote for printing only under --verbose or other explicit other information option. I would not add it to the normal operation output.

Bob
Previous: Duy Nguyen
Message 9 of 9 in “git-daemon shallow checkout fail”
  1. Bob ProulxJan 29, 2017
  2. Johannes SchindelinJan 30, 2017
  3. Bob ProulxFeb 7, 2017
  4. Jeff KingJan 30, 2017
  5. Duy NguyenFeb 2, 2017
  6. Bob ProulxFeb 7, 2017
  7. Bob ProulxFeb 7, 2017
  8. Duy NguyenFeb 7, 2017
  9. Bob ProulxFeb 7, 2017

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.