Re: TODO: git should be able to init a remote repo

From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Date: Apr 13, 2010, 19:58 UTC
Message-ID: <20100413195826.GA11597@LK-Perkele-V2.elisa-laajakaista.fi>
In-Reply-To: <i2i76718491004131030sc2f8ffa3u97a91aa9a57923b5@mail.gmail.com>

On Tue, Apr 13, 2010 at 01:30:44PM -0400, Jay Soffian wrote:

Show 16 quoted lines

> [Mostly I'm sending this so I can add a "TODO" label to it in my gmail.] :-)
> 
> With modern git, setting up a remote bare repo that you can push to is
> finally down to a reasonable number of commands:
> 
> $ ssh remote git init --bare myproject.git
> $ git remote add -m master origin remote:myproject.git
> $ git push -u origin master
> 
> But we can do better. I was thinking something like:
> 
> $ git remote init [--push] [--mirror] <name> <ssh_url>
> 
> This would perform all of the steps above, except for the push itself,
> unless given --push (in which case, that too). This is meant to
> simplify what I believe is the common case of setting up remote repos.

Couple of concerns:

- That seems awfully ssh-specific[1]...
- How remote end could deny the operation, modify paths and/or 
get post-creation notification?
- How to handle systems that would autocreate the repository anyway
if push was attempted?

[1] Well, its not like one would want to do that with gits:// anyway, since there's probably gitolite install on other end anyway...

-Ilari