From: "Alexander Gavrilov" <angavrilov@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>,
git@vger.kernel.org
Subject: Re: Init on push
Date: Sat, 8 Nov 2008 23:01:02 +0300 [thread overview]
Message-ID: <bb6f213e0811081201w22a36800j1713b91d0cf66fb2@mail.gmail.com> (raw)
In-Reply-To: <7viqqyc93w.fsf@gitster.siamese.dyndns.org>
On Sat, Nov 8, 2008 at 10:26 PM, Junio C Hamano <gitster@pobox.com> wrote:
> An easy alternative would be to issue the usual "mkdir && git init" shell
> script before spawning receive-pack. This will limit the feature to
> pushing over the ssh transport, and pushing over the git protocol against
> a loose git-daemon will not be able to support it. Also I suspect this
> will break sites managed by gitosis, where all repositories are held under
> the same UNIX user identity, differenciated only via an environment it
> sets based on the ssh key used to make the connection.
Gitosis works by replacing the shell with a program called
gitosis-serve, which parses and validates the incoming commands
against the user access configuration. If it sees an unknown command,
it will simply refuse to execute it.
On the other hand it will automatically perform initialization before
calling receive-pack if the user is authorized to write to a certain
path, but the repository does not exist yet.
Alexander
next prev parent reply other threads:[~2008-11-08 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 16:08 Init on push Robin Rosenberg
2008-11-08 19:26 ` Junio C Hamano
2008-11-08 20:01 ` Alexander Gavrilov [this message]
2008-11-08 20:12 ` Junio C Hamano
2008-11-08 20:06 ` Jakub Narebski
2008-11-08 20:08 ` Francis Galiegue
2008-11-08 20:38 ` Junio C Hamano
2008-11-08 20:44 ` Francis Galiegue
2008-11-08 20:50 ` Francis Galiegue
2008-11-09 0:13 ` Junio C Hamano
2008-11-09 1:41 ` Francis Galiegue
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=bb6f213e0811081201w22a36800j1713b91d0cf66fb2@mail.gmail.com \
--to=angavrilov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg.lists@dewire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox