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

Re: maybe breakage with latest git-pull and http protocol

From
Junio C Hamano <junkio@cox.net>
Date
Oct 13, 2005, 05:50 UTC
Message-ID
<7vr7aq55kd.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<867jciz18w.fsf@blue.stonehenge.com>
merlyn@stonehenge.com (Randal L. Schwartz) writes:
Show 7 quoted lines
> I updated git to d06b689a933f6d2130f8afdf1ac0ddb83eeb59ab,
> then compiled and installed.
>
> When I went to "git-pull" on my cogito archive (which I had edited
> to use HTTP instead of RSYNC), I got into trouble.  Unfortunately,
> I changed it to rsync to force cogito into a sane state before
> I realized that this would be a good bug report. :)

Indeed I wish we could see the set of refs you had and output from fsck-objects before the failed git-pull and after.

One thing I am aware of is that cogito repository at kernel.org is not set up to be HTTP friendly -- it lacks info/refs file git-clone uses for discovery of the available refs.

Cogito's clone/fetch over HTTP uses recursive wget for discovery, and I presume that is one of the reasons nobody noticed this. Another reason may probably be that more people use rsync transport.

Previous: Randal L. SchwartzNext: Randal L. Schwartz
Message 2 of 17 in “maybe breakage with latest git-pull and http protocol”
  1. Randal L. SchwartzOct 13, 2005
  2. Junio C HamanoOct 13, 2005
  3. Randal L. SchwartzOct 14, 2005
  4. Junio C HamanoOct 14, 2005
  5. Randal L. SchwartzOct 14, 2005
  6. Daniel BarkalowOct 14, 2005
  7. Randal L. SchwartzOct 15, 2005
  8. Junio C HamanoOct 15, 2005
  9. Junio C HamanoOct 15, 2005
  10. Daniel BarkalowOct 15, 2005
  11. Nick HengeveldOct 15, 2005
  12. Nick HengeveldOct 15, 2005
  13. Junio C HamanoOct 15, 2005
  14. Junio C HamanoOct 15, 2005
  15. Nick HengeveldOct 15, 2005
  16. Randal L. SchwartzOct 15, 2005
  17. Nick HengeveldOct 20, 2005

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.