From: Junio C Hamano <gitster@pobox.com>
To: "Alexander Gavrilov" <angavrilov@gmail.com>
Cc: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>,
git@vger.kernel.org
Subject: Re: Init on push
Date: Sat, 08 Nov 2008 12:12:34 -0800 [thread overview]
Message-ID: <7v8wruc6z1.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <bb6f213e0811081201w22a36800j1713b91d0cf66fb2@mail.gmail.com> (Alexander Gavrilov's message of "Sat, 8 Nov 2008 23:01:02 +0300")
"Alexander Gavrilov" <angavrilov@gmail.com> writes:
> 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.
If you implement a new feature by enhancing receive-pack (or anything
else), you obviously cannot use the new feature against an installation
with an older implementation, so what you said is a known. My point was
how to enhance the receiving end and what constraints we would have in
enhancing 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.
That's good to know. I also realize that gitosis does not need any hook
for "git init -D $there" to decide whether a new repository can be created
at requested location, as it reads the command line and makes decision
before driving the underlying command in response to the request.
On the other hand, people who enable 'push' access to their git-daemon
would need it, as the daemon would not even know who is asking for --init.
next prev parent reply other threads:[~2008-11-08 20:14 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
2008-11-08 20:12 ` Junio C Hamano [this message]
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=7v8wruc6z1.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=angavrilov@gmail.com \
--cc=git@vger.kernel.org \
--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