Dear John, On Sun, Oct 01 2017, John Goerzen wrote:
> The expected result here is an error, and the usual way to handle it > would be to do a git pull followed by another push attempt. > > Unfortunately, with git-remote-gcrypt, the push from repo B silently > clobbers the most recent commit made on repo A. A subsequent pull > from repo B will not pull down the changes from repo A. Could you say which backend you were using when you saw this, please? Possibly it affects all backends, but which were you able to test? Thanks. -- Sean Whitton
signature.asc
Description: PGP signature
