git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Tao Klerks <tao@klerks.biz>
To: Elijah Newren <newren@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Untracked Cache and --untracked-files=all
Date: Wed, 23 Jun 2021 08:42:10 +0200	[thread overview]
Message-ID: <CAPMMpojA7EVSuKo=Ej55H-Sk29LitEJscMuMbHHPfR7UiR4n6A@mail.gmail.com> (raw)
In-Reply-To: <CABPp-BFiwzzUgiTj_zu+vF5x20L0=1cf25cHwk7KZQj2YkVzXw@mail.gmail.com>

Hi Elijah,

On Tue, Jun 22, 2021 at 6:06 PM Elijah Newren <newren@gmail.com> wrote:
> It may be that some combination of Kyle's removal of the
> resolve_gitlink_ref() and my removal of the exponential traversal of
> untracked paths make your idea safe...but this is dir.c and
> untracked-cache, so who really knows?
>
> Not sure if that helps, but I hope one or two pointers I provided are
> somehow meaningful to you.

It is, thank you! I had already looked at those commits you mention,
and my impression is indeed that any -uall incompatibilities have been
addressed as a result of the major restructurings and fixes.

After this exchange I prepared a patch that seems to be "right" from
my perspective - it aligns the untracked cache flags with the config,
so if your command-line "-uXXX" choice matches your config you get
untracked cache, if it does not you get it disabled for that run (ie,
in windows under some circumstances, surprisingly bad performance).

This means people who want -uall to work well/performantly (because
they prefer it, or because their tooling requires it) can now have it
do so, simply by setting "git config status.showuntrackedfiles all".

This seems much better than a new temporary config, it is not subject
to "flip-flopping" issues like my previously described "naive"
approach was, and it seems much more achievable than substantially
changing the untracked cache structure & correspondingly adjusting the
untracked directory iteration process to support both -unormal and
-uall simultaneously within a single cache structure.

The patch passes all (working) tests, including the t7603 untracked
cache series I know you worked on, and seems to do exactly what I
intend it to - but I'm new here, so there are probably many problems;
hopefully this is interesting enough for people to take the time to
point them out.

The pull request in GitGitGadget is still requesting some form of
approval before I can submit the patch to the mailing list:
https://github.com/gitgitgadget/git/pull/985

Thanks,
Tao

      reply	other threads:[~2021-06-23  6:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  9:25 Untracked Cache and --untracked-files=all Tao Klerks
2021-06-22 16:06 ` Elijah Newren
2021-06-23  6:42   ` Tao Klerks [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='CAPMMpojA7EVSuKo=Ej55H-Sk29LitEJscMuMbHHPfR7UiR4n6A@mail.gmail.com' \
    --to=tao@klerks.biz \
    --cc=git@vger.kernel.org \
    --cc=newren@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.
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).