git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Lars Schneider <larsxschneider@gmail.com>,
	Francois Beutin <beutinf@ensimag.grenoble-inp.fr>,
	Git Mailing List <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 09:20:42 -0700	[thread overview]
Message-ID: <CAPc5daUTdesKcddPRtQDwO+L+qxEiE5NFv5_=2wyOH-QQ5uO1Q@mail.gmail.com> (raw)
In-Reply-To: <002b01d1b5d7$aefd0a70$0cf71f50$@nexbridge.com>

On Tue, May 24, 2016 at 9:16 AM, Randall S. Becker
<rsbecker@nexbridge.com> wrote:
> May be missing the point, but isn't the original intent to provide policy-based to control the push

I didn't get the impression that those who are proposing were
interested in a "policy that you have to obey" at all. Isn't this more
about "I often by mistake say 'git push foo' which I want to prevent"?
At least that was the impression I was getting.

  reply	other threads:[~2016-05-24 16:21 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
2016-05-24 16:07             ` Junio C Hamano
2016-05-24 16:16               ` Randall S. Becker
2016-05-24 16:20                 ` Junio C Hamano [this message]
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

  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='CAPc5daUTdesKcddPRtQDwO+L+qxEiE5NFv5_=2wyOH-QQ5uO1Q@mail.gmail.com' \
    --to=gitster@pobox.com \
    --cc=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. 
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).