3 ms·

GPG is fine, if you don't decrypt and then encrypt unless you're doing an update. So, why would it matter?

• agwa 13y ago
  If you're using GPG manually, as described in your article, then it's fine, but when you're using git filters you have no control over when encryption/decryption takes place and when it doesn't. Whenever a file is checked out from the index to the working tree, git invokes the the smudge filter, and whenever git needs to check if the file in the working tree has changed (as from `git status`), it invokes the clean filter, even if you haven't actually changed the file in the working tree[1]. If the results from the clean filter are different from what's in the index, git thinks the file has changed. That means the clean filter had better produce the same output if the working tree version hasn't actually changed. GPG doesn't satisfy that requirement. [1] newer versions of git do some caching here, so the clean filter might not always be invoked, but it's still invoked often enough to cause problems