Re: [PATCH v3] t7063: work around FreeBSD's lazy mtime update feature

2016-08-04 Thread Duy Nguyen
On Wed, Aug 3, 2016 at 9:07 PM, Junio C Hamano wrote: > Junio C Hamano writes: > >> If you mean to tell the user "I won't describe it in detail, if you >> really want to know, >> go run blame yourself", spell it out like so. I was hoping that you >> can summarize >> in-line there to help the read

Re: [PATCH v3] t7063: work around FreeBSD's lazy mtime update feature

2016-08-03 Thread Junio C Hamano
Junio C Hamano writes: > If you mean to tell the user "I won't describe it in detail, if you > really want to know, > go run blame yourself", spell it out like so. I was hoping that you > can summarize > in-line there to help the readers here. Here is a proposed fixup. t/t7063-status-untracked

Re: [PATCH v3] t7063: work around FreeBSD's lazy mtime update feature

2016-08-03 Thread Junio C Hamano
On Wed, Aug 3, 2016 at 10:45 AM, Nguyễn Thái Ngọc Duy wrote: > v3 differs from v2 in one line > > --- a/t/t7063-status-untracked-cache.sh > +++ b/t/t7063-status-untracked-cache.sh > @@ -11,7 +11,7 @@ test_description='test untracked cache' > # containing directory in sync with th

[PATCH v3] t7063: work around FreeBSD's lazy mtime update feature

2016-08-03 Thread Nguyễn Thái Ngọc Duy
Let's start with the commit message of [1] from freebsd.git [2] Sync timestamp changes for inodes of special files to disk as late as possible (when the inode is reclaimed). Temporarily only do this if option UFS_LAZYMOD configured and softupdates aren't enabled. UFS_LAZYMOD is i