From: Junio C Hamano <gitster@pobox.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Eric Wong" <e@80x24.org>, "Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [PATCH v3] t7063: work around FreeBSD's lazy mtime update feature
Date: Wed, 03 Aug 2016 12:07:58 -0700 [thread overview]
Message-ID: <xmqqpopp8ycx.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAPc5daU49iVYw14sYeshXDbHGE_nW4vWyM=2XSz-buACVLFwoA@mail.gmail.com> (Junio C. Hamano's message of "Wed, 3 Aug 2016 10:52:04 -0700")
Junio C Hamano <gitster@pobox.com> 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-cache.sh | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/t/t7063-status-untracked-cache.sh b/t/t7063-status-untracked-cache.sh
index d31d080..e0a8228 100755
--- a/t/t7063-status-untracked-cache.sh
+++ b/t/t7063-status-untracked-cache.sh
@@ -4,12 +4,16 @@ test_description='test untracked cache'
. ./test-lib.sh
-# On some filesystems (e.g. FreeBSD's ext2 and ufs) this and that
-# happens when we do blah, which forces the untracked cache code to
-# take the slow path. A test that wants to make sure the fast path
-# works correctly should call this helper to make mtime of the
-# containing directory in sync with the reality after doing blah and
-# before checking the fast path behaviour
+# On some filesystems (e.g. FreeBSD's ext2 and ufs) directory mtime
+# is updated lazily after contents in the directory changes, which
+# forces the untracked cache code to take the slow path. A test
+# that wants to make sure that the fast path works correctly should
+# call this helper to make mtime of the containing directory in sync
+# with the reality before checking the fast path behaviour.
+#
+# See <20160803174522.5571-1-pclouds@gmail.com> if you want to know
+# more.
+
sync_mtime () {
find . -type d -ls >/dev/null
}
next prev parent reply other threads:[~2016-08-03 19:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 22:30 t7063 failure on FreeBSD 10.3 i386/amd64 Eric Wong
2016-07-18 22:54 ` Eric Wong
2016-07-19 16:12 ` Duy Nguyen
2016-07-20 3:02 ` Eric Wong
2016-07-20 14:57 ` Duy Nguyen
2016-07-27 17:33 ` Duy Nguyen
2016-07-30 13:31 ` Duy Nguyen
2016-07-30 13:54 ` Duy Nguyen
2016-07-30 18:20 ` [PATCH] t7063: work around FreeBSD's lazy mtime update feature Nguyễn Thái Ngọc Duy
2016-07-31 0:15 ` Eric Wong
2016-07-31 1:07 ` Eric Wong
2016-07-31 14:30 ` Duy Nguyen
2016-08-01 1:37 ` Torstem Bögershausen
2016-08-01 17:10 ` Duy Nguyen
2016-08-01 21:04 ` Junio C Hamano
2016-08-02 15:37 ` Duy Nguyen
2016-08-02 17:17 ` Junio C Hamano
2016-08-03 16:05 ` [PATCH v2] " Nguyễn Thái Ngọc Duy
2016-08-03 16:16 ` Junio C Hamano
2016-08-03 16:25 ` Duy Nguyen
2016-08-03 17:45 ` [PATCH v3] " Nguyễn Thái Ngọc Duy
2016-08-03 17:52 ` Junio C Hamano
2016-08-03 19:07 ` Junio C Hamano [this message]
2016-08-04 15:46 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpopp8ycx.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=tboegi@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).