git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: skillzero@gmail.com
Cc: git@vger.kernel.org
Subject: Re: Per-branch receive.denyNonFastForwards?
Date: Mon, 08 Jun 2009 10:43:05 +0200	[thread overview]
Message-ID: <4A2CCF19.9000405@drmicha.warpmail.net> (raw)
In-Reply-To: <2729632a0906072220n4dff5d39vaa863401c136c3c5@mail.gmail.com>

skillzero@gmail.com venit, vidit, dixit 08.06.2009 07:20:
> Is there a way to deny non-fast forward pushes to only certain
> branches? I'd like for people to be able to force push to their own
> branches on the server, but for the master branch (and maybe a couple
> other important branches), I want to prevent it. I basically want a
> per-branch version of receive.denyNonFastForwards. Is there a way to
> do this?

The update-hook example should shows how you could guard specific
branches. If you want to make this user-dependent you may need to look
at gitosis.

Michael

      reply	other threads:[~2009-06-08  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  5:20 Per-branch receive.denyNonFastForwards? skillzero
2009-06-08  8:43 ` Michael J Gruber [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=4A2CCF19.9000405@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=skillzero@gmail.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;
as well as URLs for NNTP newsgroup(s).