From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Mahesh Vaidya <forvaidya@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git push controls / config
Date: Tue, 22 Jun 2010 10:53:22 +0000 [thread overview]
Message-ID: <AANLkTikIkyZQyvaZTUE-JzUOqKioVf_ubqBONQazP9Uf@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin8O01vNL8JlPcNqB7FdvMssjOce_YFF82iW6GC@mail.gmail.com>
On Tue, Jun 22, 2010 at 10:50, Mahesh Vaidya <forvaidya@gmail.com> wrote:
> How can I prevent (via a config file) someone from pushing a
>
> 1) same commit with --amend;
> - we rely on commit log; bug number. If some one changes bug
> number via amend; that risks the integrity.
>
> 2) creating and removing Tags and Branches
> - same - Tags are of special importance to us.
Check out some of the on-commit filters, e.g. gitosis that do this.
next prev parent reply other threads:[~2010-06-22 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 10:50 git push controls / config Mahesh Vaidya
2010-06-22 10:53 ` Ævar Arnfjörð Bjarmason [this message]
[not found] ` <AANLkTik3H-Bkkd0i71kaMFtZOQfJVDplVQHTqPoX15HE@mail.gmail.com>
2010-06-22 11:19 ` Ævar Arnfjörð Bjarmason
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=AANLkTikIkyZQyvaZTUE-JzUOqKioVf_ubqBONQazP9Uf@mail.gmail.com \
--to=avarab@gmail.com \
--cc=forvaidya@gmail.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 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).