From: Andreas Ericsson <ae@op5.se>
To: Nick Hengeveld <nickh@reactrix.com>
Cc: git@vger.kernel.org
Subject: Re: Why not clone to a remote directory over SSH
Date: Thu, 24 Nov 2005 00:15:02 +0100 [thread overview]
Message-ID: <4384F7F6.10404@op5.se> (raw)
In-Reply-To: <20051123230838.GN3968@reactrix.com>
Nick Hengeveld wrote:
> On Wed, Nov 23, 2005 at 02:16:01PM -0700, Carl Baldwin wrote:
>
>
>>It might be cool to enable cloning to a remote over ssh if the remote
>>doesn't yet exist.
>
>
> I would like to see the same for http. There is limited support for
> managing a repository using http but without the ability to run tools
> like init-db/clone/update-server-info you still need shell access
> or some other workaround. I think it would be useful to allow someone
> to create, manage, and share a repository without any special
> intelligence on the server side.
>
You'll still need to install at least git-init-db and git-receive-pack
(and git-merge, and...), even if they're run through commands from the
web. That's pretty special intelligence.
You'd also have to add some logic to enter_repo() to make it find
repositories without a HEAD correctly.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-23 23:15 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 [this message]
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
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=4384F7F6.10404@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=nickh@reactrix.com \
/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.