On Thu, Jun 28, 2018 at 05:48:01AM -0700, 1141185...@qq.com wrote:
> Thanks for reply. I know it is not a common scenario in real world, but
> when we put our valued code and docs in git, we hope git will be robust
> enough to take good care of our docs, and wont fall because of some
>
Thanks for reply. I know it is not a common scenario in real world, but
when we put our valued code and docs in git, we hope git will be robust
enough to take good care of our docs, and wont fall because of some
unconscious behavior.
在 2018年6月27日星期三 UTC+8下午4:00:21，Konstantin Khomoutov写道：
On Wed, Jun 27, 2018 at 11:00:16AM +0300, Konstantin Khomoutov wrote:
[...]
>> I have done a test in version 2.18 to test how git handle hash collision:
>> 1、I commit pdf file 'shattered-1.pdf' into my local repo. the generated
[...]
> This horse has been beaten to death already.
>
> Please
On Wed, Jun 27, 2018 at 12:29:25AM -0700, 1141185...@qq.com wrote:
> I have done a test in version 2.18 to test how git handle hash collision:
> 1、I commit pdf file 'shattered-1.pdf' into my local repo. the generated
> hash for the file is '9aaa145ccd24ef760cf31c74d8f7ca1a2e47b0' in dir 'ba'
I have done a test in version 2.18 to test how git handle hash collision:
1、I commit pdf file 'shattered-1.pdf' into my local repo. the generated
hash for the file is '9aaa145ccd24ef760cf31c74d8f7ca1a2e47b0' in dir 'ba'
2、I change the content of '9aaa145ccd24ef760cf31c74d8f7ca1a2e47b0' to
