From: Michael J Gruber <git@drmicha•warpmail.net>
To: Jeff King <peff@peff•net>
Cc: Ethan Reesor <firelizzard@gmail•com>,
Konstantin Khomoutov <kostix+git@007spb•ru>,
git <git@vger•kernel.org>
Subject: Re: Pushing a git repository to a new server
Date: Tue, 12 Feb 2013 12:28:53 +0100 [thread overview]
Message-ID: <511A2775.9050209@drmicha.warpmail.net> (raw)
In-Reply-To: <20130211162714.GB16402@sigill.intra.peff.net>
Jeff King venit, vidit, dixit 11.02.2013 17:27:
> On Mon, Feb 11, 2013 at 02:57:51AM -0500, Ethan Reesor wrote:
>
>> On Mon, Feb 11, 2013 at 2:50 AM, Konstantin Khomoutov
>> <kostix+git@007spb•ru> wrote:
>>> What's wrong with
>>> $ ssh myuser@remotehost 'mkdir /path/to/MyRepo.git; cd $_; git init --bare'
>>> $ git push --all git@remotehost:MyOtherRepo.git
>>> ?
>>
>> Nothing, I just wanted to make myself a command to do that for me.
>
> We talked about this a long time ago. One problem is that it's
> inherently unportable, as the procedure to make a repo is potentially
> different on every server (and certainly that is the case between a
> regular user running stock git and something like GitHub or Google Code;
> I imagine even gitolite has some special procedures for creating repos,
> too).
>
> One proposal made in the previous discussion was to define a microformat
> for repository administration commands. So that you could connect and
> say "git admin-create-repo /path/to/MyRepo.git", and the server-provided
> admin-create-repo command would take care of the details. Then stock git
> could forward it to "git init --bare", GitHub could do the same and
> create the necessary database records, etc.
>
> And once that standardized method was in place, it would be easy to add
> a "--create" option to "git push" to request an "admin-create-repo"
> before pushing.
>
> I still think that's a reasonable way forward, but nobody was interested
> enough to start writing code for it.
>
> -Peff
>
I'm not sure providers like GitHub would fancy an interface which allows
the programmatic creation of repos (giving a new meaning to "fork
bomb"). But I bet you know better ;-)
An alternative would be to teach git (the client) about repo types and
how to create them. After all, a repo URL "ssh://host/path" gives a
clear indication that "ssh host git init path" will create a repo. I'm
wondering whether it's more likely to convince providers (the server
side) or more is gained by covering the simpler cases client-side (our
side).
Michael
next prev parent reply other threads:[~2013-02-12 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 21:00 Pushing a git repository to a new server Ethan Reesor
2013-02-11 7:50 ` Konstantin Khomoutov
2013-02-11 7:57 ` Ethan Reesor
2013-02-11 12:45 ` Konstantin Khomoutov
2013-02-11 18:18 ` Ethan Reesor
2013-02-11 16:27 ` Jeff King
2013-02-11 18:17 ` Ethan Reesor
2013-02-12 11:28 ` Michael J Gruber [this message]
2013-02-12 20:42 ` Jeff King
2013-02-13 8:08 ` Michael J Gruber
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=511A2775.9050209@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=firelizzard@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=kostix+git@007spb$(echo .)ru \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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