Re: Git 2.7.0 gitignore behaviour regression
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Jan 7, 2016, 02:13 UTC
- Message-ID
- <CACsJy8BGskjxKKw0RGOxSzJYoA2=w_iW_cdrmKyPhpfp+AMmDw@mail.gmail.com>
- In-Reply-To
- <20160107020406.GA9358@sigill.intra.peff.net>
On Thu, Jan 7, 2016 at 9:04 AM, Jeff King <peff@peff.net> wrote:
Show 13 quoted lines
>> 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. > > Unfortunately, "importing code from us" is not so easy. :( > > They'll either need to contact the wildmatch authors, or rewrite > wildmatch from scratch.
wildmatch author relicensed it on request before [1] so he might do it again (hard to say). I'm not sure if there are other authors though. But even with wildmatch good to go, there still a lot of work to do.
[1] http://thread.gmane.org/gmane.comp.version-control.git/264312/focus=264328
-- Duy