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 (Apr 2020, #01; Wed, 15)
Date: Thu, 16 Apr 2020 08:28:02 -0700 [thread overview]
Message-ID: <CABPp-BE6xrKLA26Xn4apW-MReCeeyPKu=UMkgr4DsPW0vH4kDw@mail.gmail.com> (raw)
In-Reply-To: <xmqqr1wo4alb.fsf@gitster.c.googlers.com>
On Wed, Apr 15, 2020 at 6:13 PM Junio C Hamano <gitster@pobox.com> wrote:
> * en/fill-directory-exponential (2020-04-01) 12 commits
> - completion: fix 'git add' on paths under an untracked directory
> - Fix error-prone fill_directory() API; make it only return matches
> - dir: replace double pathspec matching with single in treat_directory()
> - dir: include DIR_KEEP_UNTRACKED_CONTENTS handling in treat_directory()
> - dir: replace exponential algorithm with a linear one
> - dir: refactor treat_directory to clarify control flow
> - dir: fix confusion based on variable tense
> - dir: fix broken comment
> - dir: consolidate treat_path() and treat_one_path()
> - dir: fix simple typo in comment
> - t3000: add more testcases testing a variety of ls-files issues
> - t7063: more thorough status checking
>
> The directory traversal code had redundant recursive calls which
> made its performance characteristics exponential with respect to
> the depth of the tree, which was corrected.
>
> Is this ready for 'next'?
I think it's as ready as it's going to get. I'm not aware of any
current issues, am not planning further work barring a report or
further review, and I'm feeling much better about it than when I first
submitted it with a bunch of big warnings (though the big warnings it
contains in that one commit message are still justified). I'm glad it
spent a good long while in pu. My biggest worry with this series is
that it might get merged just slightly before a release; I hope it
either spends an average amount of time in next and then merges down
quickly or else sits in next for a long time and merges at the
beginning of the 2.28 cycle.
Either way, at $DAYJOB I got a minor victory by getting many
volunteers who will take newish git versions (as opposed to the old
"please install at least git>=2.20.0), and I'm currently trying to set
up a pipeline for them to get new versions easily. This series will
be one of the things I include, in order generate more real-world
testing.
next prev parent reply other threads:[~2020-04-16 15:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 23:01 What's cooking in git.git (Apr 2020, #01; Wed, 15) Junio C Hamano
2020-04-16 15:28 ` Elijah Newren [this message]
2020-04-16 16:37 ` Junio C Hamano
2020-04-16 21:12 ` Damien Robert
2020-04-16 21:30 ` Jeff King
2020-04-16 22:18 ` Junio C Hamano
2020-04-16 22:47 ` Damien Robert
2020-04-16 23:05 ` Damien Robert
2020-04-16 23:34 ` Junio C Hamano
2020-04-17 12:54 ` Damien Robert
2020-04-17 17:30 ` Junio C Hamano
2020-04-17 22:04 ` Damien Robert
2020-04-17 23:22 ` Junio C Hamano
2020-04-18 17:36 ` Damien Robert
2020-04-17 2:24 ` Danh Doan
2020-04-17 5:38 ` Junio C Hamano
2020-04-17 13:36 ` Danh Doan
2020-04-17 17:40 ` 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='CABPp-BE6xrKLA26Xn4apW-MReCeeyPKu=UMkgr4DsPW0vH4kDw@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.
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).