Am 16.02.2015 um 23:10 schrieb Junio C Hamano:
> Karsten Blees writes:
>
>> However, the Makefile has this to say on the subject:
>>
>> # Define USE_NSEC below if you want git to care about sub-second file mtimes
>> # and ctimes. Note that you need recent glibc (at least 2.2.4) for this, and
>> #
Karsten Blees writes:
> However, the Makefile has this to say on the subject:
>
> # Define USE_NSEC below if you want git to care about sub-second file mtimes
> # and ctimes. Note that you need recent glibc (at least 2.2.4) for this, and
> # it will BREAK YOUR LOCAL DIFFS! show-diff and anything
Am 13.02.2015 um 20:28 schrieb Junio C Hamano:
> Karsten Blees writes:
>
>> Am 13.02.2015 um 00:38 schrieb Junio C Hamano:
>>>
>>> We do have sec/nsec fields in cache_time structure, so I have
>>> nothing against updating the msysGit port to fill that value.
>
> Having said that, we do not enabl
Karsten Blees writes:
> Am 13.02.2015 um 00:38 schrieb Junio C Hamano:
>>
>> We do have sec/nsec fields in cache_time structure, so I have
>> nothing against updating the msysGit port to fill that value.
Having said that, we do not enable the NSEC stuff by default on Unix
for a reason. I'd exp
Am 13.02.2015 um 00:38 schrieb Junio C Hamano:
> Karsten Blees writes:
>
>> This is more about copying 'old' things around, which usually also
>> copies mtime on Windows. E.g.:
>>
>> # create two files with slightly different mtime
>> for i in {1..10}; do (echo "v1" >> test); done &&
>> for
Karsten Blees writes:
> This is more about copying 'old' things around, which usually also
> copies mtime on Windows. E.g.:
>
> # create two files with slightly different mtime
> for i in {1..10}; do (echo "v1" >> test); done &&
> for i in {1..10}; do (echo "v2" >> test2); done
> # wait a
Am 12.02.2015 um 20:48 schrieb Junio C Hamano:
> Karsten Blees writes:
>
>> However, some users have expressed concerns that 'same size and
>> mtime' [2] may theoretically happen by chance in daily operation.
>
> Hmph.
>
> Haven't we already accepted that it is not just "may theoretically
> hap
Hi,
On 2015-02-12 20:48, Junio C Hamano wrote:
> Karsten Blees writes:
>
>> This patch series was inspired by the problem that Git does not
>> detect changed file content if st_size, st_mtime and st_ctime
>> are unchanged. This was apparently caused by VSS2Git resetting
>> mtime to a value in th
Karsten Blees writes:
> This patch series was inspired by the problem that Git does not
> detect changed file content if st_size, st_mtime and st_ctime
> are unchanged. This was apparently caused by VSS2Git resetting
> mtime to a value in the past. [1]
>
> I believe (or rather hope) that all invo
9 matches
Mail list logo
