[git-remote-gcrypt] --force proposal

[Sean Whitton]

Hello,

On Mon 18 May 2020 at 07:51PM +00, Jay Colson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> I believe the documentation is accurate and notes that --force is the
> 'default' behavior, so that base is covered.
>
> Maybe there is a third option which would enforce that the default behavior
> require "--force" be passed, *but* that same default behavior could be
> overridden via git-config so that wrappers and users of such could
> configure their repos to not require "--force" be passed?

This makes sense, but we're then adding quite a lot of complexity for
the sake of something which one would hope eventually gets fixed in
git-remote-gcrypt.

What do you think about the possibility of just emitting a big warning
when someone pushes without --force telling them about the bug?  Then
they can fix immediately if they didn't know that g-r-g has this
property.

-- 
Sean Whitton