From: Nick Hengeveld <nickh@reactrix.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Daniel Drake <dsd@gentoo.org>, git@vger.kernel.org
Subject: Re: HTTP repo referencing stale heads (can't clone)
Date: Mon, 3 Apr 2006 11:09:30 -0700 [thread overview]
Message-ID: <20060403180929.GA14967@reactrix.com> (raw)
In-Reply-To: <7virpqefp1.fsf@assigned-by-dhcp.cox.net>
On Mon, Apr 03, 2006 at 10:23:22AM -0700, Junio C Hamano wrote:
> My standard answer would be
>
> http-server$ cd /var/www/git/zd1211.git/ ;# or whereever
> http-server$ GIT_DIR=. git-update-server-info
Is there any interest in making the HTTP transport slighly less dumb by
using DAV?
I have a working patch to http-fetch that tries to use PROPFIND to get a
remote pack list and falls back to using objects/info/packs. It's
feasible to do something similar to get a remote ref list when cloning,
although that's a bit more work as all refs would have to be fetched
into a local repo and parsed to determine the object type.
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.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next prev parent reply other threads:[~2006-04-03 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 16:01 HTTP repo referencing stale heads (can't clone) Daniel Drake
2006-04-03 17:23 ` Junio C Hamano
2006-04-03 18:09 ` Nick Hengeveld [this message]
2006-04-04 7:03 ` Junio C Hamano
2006-04-04 10:00 ` Petr Baudis
2006-04-04 12:10 ` Nick Hengeveld
2006-04-04 15:27 ` Petr Baudis
2006-04-04 17:56 ` Nick Hengeveld
2006-04-03 18:28 ` Daniel Drake
2006-04-04 18:01 ` Nick Hengeveld
2006-04-05 12:23 ` Radoslaw Szkodzinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060403180929.GA14967@reactrix.com \
--to=nickh@reactrix.com \
--cc=dsd@gentoo.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox