git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2021, #02; Wed, 12)
Date: Wed, 12 May 2021 09:35:13 -0700	[thread overview]
Message-ID: <CABPp-BELhOx=Hi1i0GPDJoDGF_xY0UGmgn4w58v_9O=gkcb-kg@mail.gmail.com> (raw)
In-Reply-To: <xmqqo8dgfl8l.fsf@gitster.g>

On Wed, May 12, 2021 at 12:49 AM Junio C Hamano <gitster@pobox.com> wrote:

> * en/dir-traversal (2021-05-12) 8 commits
>  - dir: update stale description of treat_directory()
>  - dir: traverse into untracked directories if they may have ignored subfiles
>  - dir: avoid unnecessary traversal into ignored directory
>  - t3001, t7300: add testcase showcasing missed directory traversal
>  - t7300: add testcase showing unnecessary traversal into ignored directory
>  - ls-files: error out on -i unless -o or -c are specified
>  - dir: report number of visited directories and paths with trace2
>  - dir: convert trace calls to trace2 equivalents
>
>  "git clean" and "git ls-files -i" had confusion around working on
>  or showing ignored paths inside an ignored directory, which has
>  been corrected.
>
>  Will merge to 'next'?

Jeff had a couple small requests with the trace2 statistics, and I'll
add a patch to fix read_cached_dir() to skip '.' and '..' entries as
you suggested (and simplify various places in the code that do that
already by introducing a helper function).  So let me send out one
last reroll.

      parent reply	other threads:[~2021-05-12 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  7:46 What's cooking in git.git (May 2021, #02; Wed, 12) Junio C Hamano
2021-05-12 13:03 ` Derrick Stolee
2021-05-12 16:35 ` Elijah Newren [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='CABPp-BELhOx=Hi1i0GPDJoDGF_xY0UGmgn4w58v_9O=gkcb-kg@mail.gmail.com' \
    --to=newren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).