From: Nick Hengeveld <nickh@reactrix.com>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: HTTP repo referencing stale heads (can't clone)
Date: Tue, 4 Apr 2006 10:56:40 -0700 [thread overview]
Message-ID: <20060404175640.GE14967@reactrix.com> (raw)
In-Reply-To: <20060404152737.GN27689@pasky.or.cz>
On Tue, Apr 04, 2006 at 05:27:37PM +0200, Petr Baudis wrote:
> 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.
There are other reasons that a client can end up with a stale copy of
the server info files - in this case the problem was an intermediate
proxy out of the control of the repo admin.
While we should be able to fix that particular problem, it seems safer
to go straight to the source if possible.
> So, it really seems rather redundant to me.
If I've already enabled DAV for pushing to a repo, I'd find it nice to
be able to use it for fetches as well.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next prev parent reply other threads:[~2006-04-04 17:56 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
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 [this message]
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=20060404175640.GE14967@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.