Re: Git 2.7.0 gitignore behaviour regression

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 6, 2016, 18:58 UTC
Message-ID: <CAPc5daX+uGQfKEteT2dqax-m9dR76Gkg1YeiFjVU9dsTqnHDmw@mail.gmail.com>
In-Reply-To: <CACsJy8CvPqYGRXB845+4fHjkXH_kSAWG684CoxtWAnXE-gM6ag@mail.gmail.com>

On Wed, Jan 6, 2016 at 2:03 AM, Duy Nguyen <pclouds@gmail.com> wrote:

Show 11 quoted lines

>
> On Wed, Jan 6, 2016 at 4:50 PM, Mike McQuaid <mike@mikemcquaid.com> wrote:
> > it’s also a big area where libgit2 was inconsistent with Git’s behaviour on either of those versions too.
>
> Yeah.. it looks like libgit2's gitignore support was written new, not
> imported from C Git, so behavior differences (especially in corner
> cases) and even lack of some feature ("**" support comes to mind). For
> isolated features like gitignore, perhaps we can have an option to
> replace C Git code with libgit2 and therefore can test libgit2 against
> C Git test suite. It could be a good start for libgit2 to invade C
> Git. Not sure if anybody's interested in doing it though.

Yup, an area that is reasonably isolated from the remainder of the system like this might be a good starting point. But I suspect that the invasion needs to happen in the opposite direction in this particular case before it happens. That is, if libgit2's implementation does not behave like how we do, it needs to be fixed, possibly by discarding what they did and instead importing code from us. After the behaviour of libgit2 is fixed, we can talk about the invasion in the opposite direction.

Thanks.