Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

> On 21 Jun 2016, at 08:20, Matthieu Moy wrote: > > Antoine Queru writes: > >> However, in the last version, if we want to deny an website, >> including all schemes, we can blacklist the url without the >> scheme. For

Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

Antoine Queru writes: > However, in the last version, if we want to deny an website, > including all schemes, we can blacklist the url without the > scheme. For example, "pushBlacklist = github.com". By doing so, this > remote is not an url anymore, and it

Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

> > >> ... > >> > > > > Hello Rémi, thanks you for your input ! I'll make the appropriate changes > > and send a new version as soon as i can ! > > Hi Antoine, > > do you have an updated version already or is this the one I should look at? >

Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

>> ... >> > > Hello Rémi, thanks you for your input ! I'll make the appropriate changes > and send a new version as soon as i can ! Hi Antoine, do you have an updated version already or is this the one I should look at? http://article.gmane.org/gmane.comp.version-control.git/296445 Thanks,

Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

Matthieu Moy writes: >> + *easier and avoid confusion with a distant repo like 'github.com' Forgotten nit in previous message: s/distant/remote/. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in

Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

Matthieu Moy writes: > Antoine Queru writes: > >> Currently, a user wanting to prevent accidental pushes to the wrong >> remote has to create a pre-push hook. The feature > > It's not clear what "The feature" refers to. Given the

Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

Antoine Queru writes: > Currently, a user wanting to prevent accidental pushes to the wrong > remote has to create a pre-push hook. The feature It's not clear what "The feature" refers to. Given the context, I read it as "pre-push hook", but I think this is not

Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

- Mail original - > Hi Antoine, > > Antoine Queru writes: > > [...] > > +For example, if we set up the configuration variables like this: > > + > > +--- > > +git config --add remote.pushBlacklist repository.com > > +git config

Re: [RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

Hi Antoine, Antoine Queru writes: > [...] > +For example, if we set up the configuration variables like this: > + > +--- > +git config --add remote.pushBlacklist repository.com > +git config --add remote.pushWhitelist

[RFC/PATCH] push: deny policy to prevent pushes to unwanted remotes.

Currently, a user wanting to prevent accidental pushes to the wrong remote has to create a pre-push hook. The feature offers a configuration to allow users to prevent accidental pushes to the wrong remote. The user may define a list of whitelisted remotes, a list of blacklisted remotes and a