From: "Jakub Narębski" <jnareb@gmail.com>
To: Stefan Beller <sbeller@google.com>, Thorsten Glaser <t.glaser@tarent.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Server-side preventing some files from being overwritten
Date: Thu, 21 Jul 2016 13:21:57 +0200 [thread overview]
Message-ID: <5790B055.4060603@gmail.com> (raw)
In-Reply-To: <CAGZ79kb=2rpYucjhavNB_XHLk9rjKSoHzL9bwM5buDO0GyW3vw@mail.gmail.com>
W dniu 2016-07-14 o 18:57, Stefan Beller pisze:
> On Thu, Jul 14, 2016 at 8:31 AM, Thorsten Glaser <t.glaser@tarent.de> wrote:
>> Hi *,
>>
>> is there a way, for example with some sort of pre-receive hook,
>> to prevent some files from being overwritten by a push?
>
> pre-receive hooks are a thing!
Or you can use third-party tools with support for such cases, such
as Gitolite. VREFs allow to restrict pushes by the filename, see
http://gitolite.com/gitolite/vref.html#NAME (though I am not sure
if it checks only the end state, or if it checks every commit
that was pushed).
Best,
--
Jakub Narębski
next prev parent reply other threads:[~2016-07-21 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 15:31 Server-side preventing some files from being overwritten Thorsten Glaser
2016-07-14 16:57 ` Stefan Beller
2016-07-14 17:51 ` Thorsten Glaser
2016-07-14 18:27 ` Junio C Hamano
2016-07-14 18:44 ` Junio C Hamano
2016-07-14 18:50 ` Stefan Beller
2016-07-15 13:56 ` Ævar Arnfjörð Bjarmason
2016-07-15 15:30 ` Thorsten Glaser
2016-07-14 18:50 ` Thorsten Glaser
2016-07-14 19:10 ` Junio C Hamano
2016-07-21 11:21 ` Jakub Narębski [this message]
2016-07-21 12:27 ` Thorsten Glaser
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5790B055.4060603@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=t.glaser@tarent.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).