From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Francois Beutin <beutinf@ensimag.grenoble-inp.fr>,
"Randall S. Becker" <rsbecker@nexbridge.com>,
git@vger.kernel.org,
simon rabourg <simon.rabourg@ensimag.grenoble-inp.fr>,
wiliam duclot <wiliam.duclot@ensimag.grenoble-inp.fr>,
antoine queru <antoine.queru@ensimag.grenoble-inp.fr>
Subject: Re: [Opinion gathering] Git remote whitelist/blacklist
Date: Tue, 24 May 2016 14:55:50 +0200 [thread overview]
Message-ID: <vpq37p74nu1.fsf@anie.imag.fr> (raw)
In-Reply-To: <84BDC4A4-FBE1-4542-868C-FA77A25469F3@gmail.com> (Lars Schneider's message of "Tue, 24 May 2016 06:55:31 -0400")
Lars Schneider <larsxschneider@gmail.com> writes:
> To answer your question,
> I would reject the push (because the remote is in the denied list) and
> print a warning to point out the conflicting configs to the user.
So, when trying a forbidden push, Git would deny it and the only way to
force the push would be to remove the blacklist from the config, right?
Probably the sanest way to go. I thought about adding a "git push
--force-even-if-in-blacklist" or so, but I don't think the feature
deserves one specific option (hence add some noise in `git push -h`).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-05-24 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1040142021.5607762.1463753271105.JavaMail.zimbra@ensimag.grenoble-inp.fr>
2016-05-20 14:21 ` [Opinion gathering] Git remote whitelist/blacklist Francois Beutin
2016-05-20 14:22 ` Randall S. Becker
2016-05-23 12:51 ` Francois Beutin
2016-05-24 10:12 ` Francois Beutin
2016-05-24 10:55 ` Lars Schneider
2016-05-24 12:55 ` Matthieu Moy [this message]
2016-05-24 16:07 ` Junio C Hamano
2016-05-24 16:16 ` Randall S. Becker
2016-05-24 16:20 ` Junio C Hamano
2016-05-24 19:25 ` Lars Schneider
2016-05-24 21:02 ` Randall S. Becker
2016-05-24 19:11 ` Lars Schneider
2016-05-24 19:22 ` Matthieu Moy
2016-05-25 22:52 ` Jeff King
2016-05-24 22:24 ` Aaron Schrab
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=vpq37p74nu1.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=antoine.queru@ensimag.grenoble-inp.fr \
--cc=beutinf@ensimag.grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=rsbecker@nexbridge.com \
--cc=simon.rabourg@ensimag.grenoble-inp.fr \
--cc=wiliam.duclot@ensimag.grenoble-inp.fr \
/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.