I have use 0.4 version of git-crypt for many years, it's works well with git 1.9, but recently github.com need tls1.2 which force me to update git to 2.x, and I found 0.4 not works with git 2.x, so I updated git-crypt to 0.5 and I found 2 bugs at least.
On winodws, if path of the repo has unicode, git-crypt unlock will fail, due to git 2.x output utf-8 chars in the result of git ls-files, this will let touch_file fail on windows platform
If the repo has many files, git_checkout will failed on windows, due the command of launching process are too long.
Solution:
I find out another solution for touch_file, that's git rm -r .
'git checkout -f HEAD -- .' works well in 0.4
So I modified the source of 0.4, just add git rm -r . for touch_file, it works well with git 2.x!
Sorry I don't need other features above 0.4.
I have use 0.4 version of git-crypt for many years, it's works well with git 1.9, but recently github.com need tls1.2 which force me to update git to 2.x, and I found 0.4 not works with git 2.x, so I updated git-crypt to 0.5 and I found 2 bugs at least.
On winodws, if path of the repo has unicode,
git-crypt unlock
will fail, due to git 2.x output utf-8 chars in the result ofgit ls-files
, this will lettouch_file
fail on windows platformIf the repo has many files,
git_checkout
will failed on windows, due the command of launching process are too long.Solution:
touch_file
, that'sgit rm -r .
So I modified the source of 0.4, just add
git rm -r .
fortouch_file
, it works well with git 2.x! Sorry I don't need other features above 0.4.