From: Felipe Contreras <felipe.contreras@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: Regression in git ls-files, or bug in completion?
Date: Tue, 31 Mar 2020 16:54:12 -0600 [thread overview]
Message-ID: <CAMP44s2FT07h1rGffP59U_8663Y1SM+dJ4mMaU7k2MjHmeTJFg@mail.gmail.com> (raw)
In-Reply-To: <CABPp-BG6QQV5aMbrUhB+mCU_fErwLY5uYHzi6DKV5jkPd1p8DA@mail.gmail.com>
On Sat, Mar 28, 2020 at 11:22 AM Elijah Newren <newren@gmail.com> wrote:
>
> On Sat, Mar 28, 2020 at 6:25 AM Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> >
> > On Sun, Mar 22, 2020 at 5:39 PM Felipe Contreras
> > <felipe.contreras@gmail.com> wrote:
> >
> > > I noticed a possible regression caused by commit b9670c1f5e (dir: fix
> > > checks on common prefix directory).
> >
> > > Before it was "empty", now it is "./".
> >
> > I guess you don't care about this regression.
>
> Sorry for being slow to get back to you; it wasn't that I didn't care
> (I marked the message as important to return to) but that I was
> focused on 2.26 regressions and other fixes I've been promising for
> months. I'm working on a fix for this 2.25 regression, but note that
> it's going to depend on this series:
> https://lore.kernel.org/git/pull.700.v4.git.git.1585258061.gitgitgadget@gmail.com/
I see. Please let me know when you have something ready to test.
--
Felipe Contreras
prev parent reply other threads:[~2020-03-31 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 23:39 Regression in git ls-files, or bug in completion? Felipe Contreras
2020-03-28 13:25 ` Felipe Contreras
2020-03-28 17:22 ` Elijah Newren
2020-03-31 22:54 ` Felipe Contreras [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s2FT07h1rGffP59U_8663Y1SM+dJ4mMaU7k2MjHmeTJFg@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).