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, 15:27 UTC
Message-ID
<20060404152737.GN27689@pasky.or.cz>
In-Reply-To
<20060404121056.GB14967@reactrix.com>

Dear diary, on Tue, Apr 04, 2006 at 02:10:57PM CEST, I got a letter where Nick Hengeveld <nickh@reactrix.com> said that...

Show 8 quoted lines
> On Tue, Apr 04, 2006 at 12:00:35PM +0200, Petr Baudis wrote:
> 
> > Well, what is the actual advantage of DAV compared to
> > git-update-server-info? Why would I prefer enabling DAV?
> 
> In theory, things should work the same either way.  It seems that in
> practice though, the server info files continue to surface as a source
> of fetch problems.

Because people do not know they have to set up their post-update hook. When they are already going at lengths to find out how to set up DAV for git fetch, they would discover the post-update hook way as well.

So, it really seems rather redundant to me.
-- 
				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: Nick HengeveldNext: Nick Hengeveld
Message 7 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.