From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Jörn Engel" <joern@purestorage.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: new file mode 160000
Date: Tue, 10 Mar 2020 22:22:56 +0000 [thread overview]
Message-ID: <20200310222256.GA6198@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20200310195724.GE1443@cork>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On 2020-03-10 at 19:57:24, Jörn Engel wrote:
> That is indeed the content. So no bug in git. Thank you!
>
> Given that we don't want to use submodules for this particular
> project, can the git server be configured to refuse push requests that
> would introduce submodules?
I don't believe there's an option to do this, but it could be achieved
with a pre-receive hook. That's the usual approach for denying pushes
containing unwanted data (submodules, large files, commits with
improperly formatted messages, etc.).
If your Git server doesn't let you install pre-receive hooks, you can do
this by adding a test to your CI system to reject objectionable pushes.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2020-03-10 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 18:41 new file mode 160000 Jörn Engel
2020-03-10 19:10 ` Andreas Schwab
2020-03-10 19:47 ` Junio C Hamano
2020-03-10 20:09 ` Andreas Schwab
2020-03-11 18:35 ` Junio C Hamano
2020-03-10 19:37 ` Bryan Turner
2020-03-10 19:46 ` Junio C Hamano
2020-03-10 19:57 ` Jörn Engel
2020-03-10 22:22 ` brian m. carlson [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=20200310222256.GA6198@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joern@purestorage.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 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.