[git-remote-gcrypt] --force proposal

[Sean Whitton]

Hello Jay,

On Fri 15 May 2020 at 12:20AM +01, Jay Colson wrote:

> https://github.com/spwhitton/git-remote-gcrypt/pull/4/commits/2e9472a680b8b37af3b6cd79ae1731167d2991ad
>
> pr to get reminded that we should --force pushes ... as each is
> 'really' a [force] push (according to documentation), this seems like
> a way to 'remind' users of that

I can't apply this patch since it is not signed off.  Please see
CONTRIBUTING.rst.

Stepping back: the proposal is to require explicitly passing --force for
pushes since all pushes with git-remote-gcrypt implicitly have --force.

I am not sure this is a great idea, because if someone fixes
git-remote-gcrypt so that it does not always force-push, users who have
hardcoded --force into their scripts will not be able to benefit from
that.

I'd like to get feedback from other users.  I've CCed Joey as the
maintainer of git-annex, which is the source of a lot of
git-remote-gcrypt's users.

-- 
Sean Whitton