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

HTTP questions

From
NHNick Hengeveld <nickh@reactrix.com>
Date
Jun 1, 2006, 23:24 UTC
Message-ID
<20060601232437.GD12261@reactrix.com>

While testing recent http-fetch changes with a current checkout of next, I noticed a couple of things:

- "git push" seems to pass --thin by default to http-push, which
  subsequently barfs because that's not a valid http-push option.
  Should it be?  Should it be silently ignored?  Should git-push not
  default to --thin when pushing with HTTP transport?
- when I clone, http-fetch outputs a whole bunch of 
  "error: Could not read ..." messages - is that expected?
-- 
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
Next: Junio C Hamano
Message 1 of 9 in “HTTP questions”
  1. Nick HengeveldJun 1, 2006
  2. Junio C HamanoJun 2, 2006
  3. http-fetch troublesJunio C Hamano, Jun 2, 2006
  4. Junio C HamanoJun 2, 2006
  5. Linus TorvaldsJun 2, 2006
  6. Becky BruceJun 3, 2006
  7. Junio C HamanoJun 3, 2006
  8. Linus TorvaldsJun 3, 2006
  9. Junio C HamanoJun 3, 2006

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.