[EXT]Re: [git-remote-gcrypt] --force proposal
Jay Colson
jay at karma.net
Fri May 29 15:43:39 BST 2020
Perfect. Here is the patch:
https://github.com/spwhitton/git-remote-gcrypt/commit/1181f79614a356170a2fd1de933742c10a0163fe
Cheers,
Jay Colson
On Wed, May 27, 2020 at 8:36 PM Sean Whitton <spwhitton at email.arizona.edu>
wrote:
> Hello Jay,
>
> On Wed 20 May 2020 at 02:02AM -07, Jay Colson wrote:
>
> > Sean,
> > May I offer another option? Allowing git-config to configure the
> ability
> > to abort if --force was not passed (so the opposite of the configuration
> I
> > previously mentioned). Defaulting to your proposal (emitting a warning)
> if
> > the configuration flag was not set, but aborting if the flag was set.
> > Perhaps:
> >
> > `gcrypt.force-required=true`
>
> I'm okay with adding this, as it nicely becomes a noop if and when
> git-remote-gcrypt learns how to non-force push.
>
> --
> Sean Whitton
>
--
<+353866993893>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.chiark.greenend.org.uk/pipermail/sgo-software-discuss/attachments/20200529/7a0a86be/attachment.html>
More information about the sgo-software-discuss
mailing list