From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/5] nd/fix-untracked-cache-invalidation updates
Date: Wed, 24 Jan 2018 12:47:57 +0100 [thread overview]
Message-ID: <87d11zh40i.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20180124093023.9071-1-pclouds@gmail.com>
On Wed, Jan 24 2018, Nguyễn Thái Ngọc Duy jotted:
> This is a small update where the last two patches on 'pu' are merged
> in one. The final content is exactly the same as on 'pu'.
>
> Nguyễn Thái Ngọc Duy (3):
> dir.c: avoid stat() in valid_cached_dir()
> dir.c: fix missing dir invalidation in untracked code
> dir.c: stop ignoring opendir() error in open_cached_dir()
>
> Ævar Arnfjörð Bjarmason (2):
> status: add a failing test showing a core.untrackedCache bug
> update-index doc: note a fixed bug in the untracked cache
Looks good to me.
next prev parent reply other threads:[~2018-01-24 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 9:50 [PATCH] dir.c: print correct errno when opendir() fails Nguyễn Thái Ngọc Duy
2018-01-19 21:09 ` Junio C Hamano
2018-01-21 11:52 ` Duy Nguyen
2018-01-24 9:30 ` [PATCH 0/5] nd/fix-untracked-cache-invalidation updates Nguyễn Thái Ngọc Duy
2018-01-24 9:30 ` [PATCH 1/5] status: add a failing test showing a core.untrackedCache bug Nguyễn Thái Ngọc Duy
2018-01-24 9:30 ` [PATCH 2/5] dir.c: avoid stat() in valid_cached_dir() Nguyễn Thái Ngọc Duy
2018-01-24 9:30 ` [PATCH 3/5] dir.c: fix missing dir invalidation in untracked code Nguyễn Thái Ngọc Duy
2018-01-24 9:30 ` [PATCH 4/5] update-index doc: note a fixed bug in the untracked cache Nguyễn Thái Ngọc Duy
2018-01-24 9:30 ` [PATCH 5/5] dir.c: stop ignoring opendir() error in open_cached_dir() Nguyễn Thái Ngọc Duy
2018-02-01 23:00 ` Ævar Arnfjörð Bjarmason
2018-01-24 11:47 ` Ævar Arnfjörð Bjarmason [this message]
2018-01-24 20:41 ` [PATCH 0/5] nd/fix-untracked-cache-invalidation updates Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d11zh40i.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
/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.
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 NNTP newsgroup(s).