From: Nick Hengeveld <nickh@reactrix.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Andreas Ericsson <ae@op5.se>, git@vger.kernel.org
Subject: Re: Why not clone to a remote directory over SSH
Date: Fri, 25 Nov 2005 12:26:40 -0800 [thread overview]
Message-ID: <20051125202640.GS3968@reactrix.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0511241136370.12985@wbgn013.biozentrum.uni-wuerzburg.de>
On Thu, Nov 24, 2005 at 11:36:58AM +0100, Johannes Schindelin wrote:
> > > For that matter, is it possible to generate the file(s) needed for a dumb
> > > server on the client side?
> >
> > Which files are those? I've been working on a way to update info/refs
> > and eventually objects/info/packs.
>
> These I meant.
Yes - it should be straightforward to generate those files on the client
side. A PROPFIND request for the remote directory with Depth: 1 will
return a list of files in the directory, so refs and objects/packs can
be crawled to generate the contents of the server info files. That's
assuming that packs and tags are being pushed of course.
Come to think of it, PROPFIND is probably a more efficient way to check
for the existence of an object in the remote repo as well. That would
make it feasible to remove the --complete option and always verify the
full history.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next prev parent reply other threads:[~2005-11-25 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 21:16 Why not clone to a remote directory over SSH Carl Baldwin
2005-11-23 23:08 ` Nick Hengeveld
2005-11-23 23:15 ` Andreas Ericsson
2005-11-23 23:28 ` Nick Hengeveld
2005-11-23 23:45 ` Johannes Schindelin
2005-11-24 1:04 ` Nick Hengeveld
2005-11-24 10:36 ` Johannes Schindelin
2005-11-25 20:26 ` Nick Hengeveld [this message]
2005-11-23 23:26 ` Junio C Hamano
2005-11-23 23:41 ` Johannes Schindelin
2005-11-24 0:19 ` Nick Hengeveld
2005-11-24 8:14 ` Andreas Ericsson
2005-11-24 0:51 ` Linus Torvalds
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=20051125202640.GS3968@reactrix.com \
--to=nickh@reactrix.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).