In fact it seems clear that if use by default OpenTimestamps gpg wrapper, then we only have an issue of potential conflict with encrypted repositories but this is an edge case potentially fine with disabling OpenTimestamps usage on, at least for the moment.
See Benjamin-Loison/git-remote-gcrypt/issues/15.
In fact it seems clear that if use by default OpenTimestamps gpg wrapper, then we only have an issue of potential conflict with encrypted repositories but this is an edge case potentially fine with disabling OpenTimestamps usage on, at least for the moment.
Related to #2.