[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature
From:       Duy Nguyen <pclouds () gmail ! com>
Date:       2016-07-31 14:30:34
Message-ID: CACsJy8CfLYPT5hJRT1q6nCtjy0K6+nZWGV5G+d7u=ymuEZ85tg () mail ! gmail ! com
[Download RAW message or body]

On Sun, Jul 31, 2016 at 3:07 AM, Eric Wong <e@80x24.org> wrote:
>> would be more to the point of what is going on, here.   But I
>> also wonder if untracked cache itself could/should be doing this
>> internally.
>
> Still wondering :>

There's nothing we can do besides maybe run a cron job executing
'sync' every second or so. We need to force mtime to be written down
close to.. you know.. mtime. By the time git is executed, it's already
late. You can execute 'sync' inside git then wait a couple seconds..
but that's just stupid. And removing the racy check is even more
dangerous, now you can get false output.
-- 
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]