Re: [RFC PATCH 0/5] Fix some fast-import parsing issues
- From
Elijah Newren <newren@gmail.com>
- Date
- Apr 1, 2019, 15:52 UTC
- Message-ID
- <CABPp-BEHiYddGzVfuQoiN403na2dOSXBbnJDffp3pPsEqQ2Pgw@mail.gmail.com>
- In-Reply-To
- <xmqqwokevwbb.fsf@gitster-ct.c.googlers.com>
On Mon, Apr 1, 2019 at 3:44 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 19 quoted lines
> > Elijah Newren <newren@gmail.com> writes: > > > On Wed, Feb 20, 2019 at 2:58 PM Elijah Newren <newren@gmail.com> wrote: > >> > >> I found a few issues with parsing in fast-import (dating back to > > .... > >> I've cc'ed the relevant folks, and have a few patches that fix the > >> issue and I think make the parser more robust against future issues in > >> a way that I think is safe enough for backward compatibility, but > >> "backward compatible enough" might concern some folks; if so, please > >> take a look at patches 4 and 5. > > > > Just thought I'd ping to see if folks have any concerns with this > > slight tweak to backward compatibility; if not, I'll just repost the > > patches removing the RFC label. > > It's been more than a month and we haven't hard from anybody, > perhaps?
Indeed; I was going to resend sooner but got wrapped up in directory-rename-conflict-by-default, switch and restore series discussions, etc. I'll rip off the RFC label and resend.