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

Re: HTTP repo referencing stale heads (can't clone)

From
Petr Baudis <pasky@suse.cz>
Date
Apr 4, 2006, 10:00 UTC
Message-ID
<20060404100035.GM27689@pasky.or.cz>
In-Reply-To
<20060403180929.GA14967@reactrix.com>

Dear diary, on Mon, Apr 03, 2006 at 08:09:30PM CEST, I got a letter where Nick Hengeveld <nickh@reactrix.com> said that...

> Long term, this could give a repo admin the choice of either making sure
> git-update-server-info has been run after every ref/pack change or
> enabling DAV once.  Assuming they need to use HTTP.

Well, what is the actual advantage of DAV compared to git-update-server-info? Why would I prefer enabling DAV?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Right now I am having amnesia and deja-vu at the same time.  I think
I have forgotten this before.
Previous: Junio C HamanoNext: Nick Hengeveld
Message 5 of 11 in “HTTP repo referencing stale heads (can't clone)”
  1. Daniel DrakeApr 3, 2006
  2. Junio C HamanoApr 3, 2006
  3. Nick HengeveldApr 3, 2006
  4. Junio C HamanoApr 4, 2006
  5. Petr BaudisApr 4, 2006
  6. Nick HengeveldApr 4, 2006
  7. Petr BaudisApr 4, 2006
  8. Nick HengeveldApr 4, 2006
  9. Daniel DrakeApr 3, 2006
  10. Nick HengeveldApr 4, 2006
  11. Radoslaw SzkodzinskiApr 5, 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.