From: Alex Riesen <raa.lkml@gmail.com>
To: Ishaaq Chandy <ishaaq@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: disable branch modification
Date: Tue, 4 Aug 2009 18:50:51 +0200 [thread overview]
Message-ID: <81b0412b0908040950j1aa8ca04t68061a79c96f6522@mail.gmail.com> (raw)
In-Reply-To: <24550469.post@talk.nabble.com>
On Sat, Jul 18, 2009 at 20:16, Ishaaq Chandy<ishaaq@gmail.com> wrote:
> 1. Create new branches on it
> 2. Delete existing branches from it
You cannot have these.
> 3. push non-fast-forward commits to it.
>
> I think I'll need to write a pre-receive hook for this, but before I embark
> on this, any helpful pointers would be appreciated.
Look in the mailing list archives for pre-receive, update and SSH,
there were some good examples of update and pre-receive posted.
Also, there is contrib/hooks/update-paranoid in Git repo. It
implements an ACL per SSH user.
prev parent reply other threads:[~2009-08-04 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 18:16 disable branch modification Ishaaq Chandy
2009-08-04 13:36 ` Andreas Ericsson
2009-08-04 16:50 ` Alex Riesen [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=81b0412b0908040950j1aa8ca04t68061a79c96f6522@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=ishaaq@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).