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

HTTP pushes

From
NHNick Hengeveld <nickh@reactrix.com>
Date
Nov 1, 2005, 02:02 UTC
Message-ID
<20051101020248.GA3928@reactrix.com>

HTTP is currently listed as a read-only/unsupported method for doing pushes, is that due to inherent problems with HTTP or just because it hasn't been written yet?

I've built a working prototype of an HTTP push implementation using DAV. It locks the remote branch file during the push and PUTs to temp files to insure nobody else reads objects while they're being pushed. It does not validate remote objects - if they exist on the remote end as loose objects or in a pack, local copies won't be pushed. It supports sparse object directories, and verifies that the remote branch is an ancestor of the local branch before doing anything.

I'm curious to know whether it would be useful to proceed further, and to know what I haven't thought about yet...

-- 
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
Next: Johannes Schindelin
Message 1 of 8 in “HTTP pushes”
  1. Nick HengeveldNov 1, 2005
  2. Johannes SchindelinNov 1, 2005
  3. Junio C HamanoNov 2, 2005
  4. David LangNov 2, 2005
  5. Nick HengeveldNov 2, 2005
  6. Johannes SchindelinNov 2, 2005
  7. Daniel BarkalowNov 1, 2005
  8. H. Peter AnvinNov 3, 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.