From: "Tajti Ákos" <akos.tajti@intland.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-smart-http reject push
Date: Fri, 01 Jun 2012 08:52:58 +0200 [thread overview]
Message-ID: <4FC866CA.1080203@intland.com> (raw)
In-Reply-To: <CAMK1S_iAxdTg04ctZMUKAyoBRGT=w8rp2dTMDFvmpW_McPP-hQ@mail.gmail.com>
Thanks for the answers!
Ákos
2012.06.01. 5:53 keltezéssel, Sitaram Chamarty írta:
> On Fri, Jun 1, 2012 at 2:08 AM, Tajti Ákos<akos.tajti@intland.com> wrote:
>> Dear List,
>>
>> we wrote a servlet that is basically a proxy for git-http-backend. We want
>> to control who can create a new branch. Is there a way to reject a push that
>> would create a new branch (without using hooks)?
> Not sure what else your servlet does or how it affects things but
> gitolite has controls to prevent branches being created (among many
> many other things, limited mostly by ones imagination!).
>
> Gitolite is normally used with ssh but it has been tested with smart
> http also. It itself acts as a proxy for git-http-backend, inspecting
> the URI and QUERY_STRING and such animals to decode some things, while
> the rest happens via a special update hook that is installed in each
> repo that it controls.
>
> (Specifically, the branch create check is done there, not in the part
> that is proxying the git-http-backend process. You probably know that
> the update hook is invoked by git itself).
>
> Sitaram
prev parent reply other threads:[~2012-06-01 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 20:38 git-smart-http reject push Tajti Ákos
2012-05-31 20:52 ` Shawn Pearce
2012-06-01 3:53 ` Sitaram Chamarty
2012-06-01 6:52 ` Tajti Ákos [this message]
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=4FC866CA.1080203@intland.com \
--to=akos.tajti@intland.com \
--cc=git@vger.kernel.org \
/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.