Re: Regression in git ls-files, or bug in completion?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Regression in git ls-files, or bug in completion?
From: Felipe Contreras <felipe.contreras@xxxxxxxxx>
Date: Sat, 28 Mar 2020 07:25:34 -0600
Cc: Elijah Newren <newren@xxxxxxxxx>, Junio C Hamano <gitster@xxxxxxxxx>
In-reply-to: <CAMP44s2XuXrgBztke50YgnZ1SQh6gvR6cdLz064xDDK3+s2CSA@mail.gmail.com>
References: <CAMP44s2XuXrgBztke50YgnZ1SQh6gvR6cdLz064xDDK3+s2CSA@mail.gmail.com>

On Sun, Mar 22, 2020 at 5:39 PM Felipe Contreras
<felipe.contreras@xxxxxxxxx> 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.

-- 
Felipe Contreras

Follow-Ups:
- Re: Regression in git ls-files, or bug in completion?
  - From: Elijah Newren

References:
- Regression in git ls-files, or bug in completion?
  - From: Felipe Contreras

Prev by Date: Re: [PATCH v3 1/1] remote.c: fix handling of %(push:remoteref)
Next by Date: Re: [PATCH v3 1/1] remote.c: fix handling of %(push:remoteref)
Previous by thread: Regression in git ls-files, or bug in completion?
Next by thread: Re: Regression in git ls-files, or bug in completion?
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux