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

Re: Debugging a bizarre problem: What can influence 'git fetch'?

From
Tay Ray Chuan <rctay89@gmail.com>
Date
Mar 2, 2013, 10:32 UTC
Message-ID
<CALUzUxoFwpi6J3TKTaxuCjLumOkyhWFLqz6k_23X4P0xpwD26A@mail.gmail.com>
In-Reply-To
<20130301143940.7e31f0c2@copperhead.int.arc7.info>
On Fri, Mar 1, 2013 at 10:39 PM,  <git-users@io7m.com> wrote:
> Is there some way to get 'git fetch'
> to be more verbose?

It seems that the remote is running the 'dumb' http protocol, you might want to try setting the GIT_CURL_VERBOSE environment variable for more verbosity.

Have you tried running git-update-server-info on the remote side? Perhaps a push/fetch led to packs being created so the f981a2b object isn't available as a loose object but in a pack but the remote still indicates otherwise.

-- Cheers, Ray Chuan

Previous: git-users@io7m.comNext: git-users@io7m.com
Message 2 of 3 in “Debugging a bizarre problem: What can influence 'git fetch'?”
  1. git-users@io7m.comMar 1, 2013
  2. Tay Ray ChuanMar 2, 2013
  3. git-users@io7m.comMar 2, 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.