From: Ben Peart <peartben@gmail.com>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: Ben Peart <benpeart@microsoft.com>,
git@vger.kernel.org, pclouds@gmail.com, bmwill@google.com,
avarab@gmail.com
Subject: Re: [PATCH v1] dir.c: don't flag the index as dirty for changes to the untracked cache
Date: Thu, 1 Mar 2018 07:35:28 -0500 [thread overview]
Message-ID: <a43a4408-6889-772a-58bf-c1b2feb7cf51@gmail.com> (raw)
In-Reply-To: <20180301074245.GF31079@sigill.intra.peff.net>
On 3/1/2018 2:42 AM, Jeff King wrote:
> On Wed, Feb 28, 2018 at 01:27:03PM -0800, Junio C Hamano wrote:
>
>> Somehow this topic has been hanging without getting further
>> attention for too long. It's time to wrap it up and moving it
>> forward. How about this?
>>
>> -- >8 --
>> From: Junio C Hamano <gitster@pobox.com>
>> Date: Wed, 28 Feb 2018 13:21:09 -0800
>> Subject: [PATCH] untracked cache: use git_env_bool() not getenv() for customization
>> [...]
>
> This looks good to me. Thanks for tying up the loose end.
>
> -Peff
>
Looks good to me as well. Thanks for fixing the environment variables.
I'm having send-email issues so hope this one gets through. Please
ignore my [PATCH V2] if it ever makes it through.
Ben
prev parent reply other threads:[~2018-03-01 12:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 19:56 [PATCH v1] dir.c: don't flag the index as dirty for changes to the untracked cache Ben Peart
2018-02-05 20:55 ` Junio C Hamano
2018-02-06 1:39 ` Ben Peart
2018-02-05 21:58 ` Brandon Williams
2018-02-06 1:48 ` Ben Peart
2018-02-06 12:27 ` Duy Nguyen
2018-02-06 12:55 ` Duy Nguyen
2018-02-07 10:59 ` Duy Nguyen
2018-02-07 13:46 ` Ben Peart
2018-02-06 14:50 ` Junio C Hamano
2018-02-07 14:13 ` Ben Peart
2018-02-12 10:20 ` Duy Nguyen
2018-02-12 17:57 ` Ben Peart
2018-02-13 9:57 ` Duy Nguyen
2018-02-08 10:33 ` Jeff King
2018-02-28 21:27 ` Junio C Hamano
2018-03-01 7:42 ` Jeff King
2018-03-01 12:35 ` Ben Peart [this message]
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=a43a4408-6889-772a-58bf-c1b2feb7cf51@gmail.com \
--to=peartben@gmail.com \
--cc=avarab@gmail.com \
--cc=benpeart@microsoft.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).