Re: [PATCH 0/2] Fix merge restore state
- From
Elijah Newren <newren@gmail.com>
- Date
- Jun 12, 2022, 06:58 UTC
- Message-ID
- <CABPp-BHfdo_JK-NyhMv=_7FpAGNj_vxGwGRoSYXRK==ARzh1Cw@mail.gmail.com>
- In-Reply-To
- <pull.1231.git.1652977582.gitgitgadget@gmail.com>
On Thu, May 19, 2022 at 9:26 AM Elijah Newren via GitGitGadget <gitgitgadget@gmail.com> wrote:
> > A simple series to fix restore_state() in builtin/merge.c, fixing the issue > reported by ZheNing Hu over here: > https://lore.kernel.org/git/CAOLTT8R7QmpvaFPTRs3xTpxr7eiuxF-ZWtvUUSC0-JOo9Y+SqA@mail.gmail.com/
I updated this series a few weeks ago, I believe addressing all the feedback. But I hesitated to type "/submit" over at https://github.com/gitgitgadget/git/pull/1231. I've done virtually no development on "interesting" (to me) projects for quite some time; I'm only responding to email questions and review requests on the list. And the review process takes quite a bit of work at times, and on the chance there was more feedback to address, I just didn't have it in me to submit a new round even though it _might_ be complete and certainly fixes some known issues. I haven't even gotten to review Dscho's updates of my patches this whole week (spent the time I had mostly on the merge-ort issue reported).
Does anyone else want to take this topic over? There are updated patches and even an updated cover letter over at https://github.com/gitgitgadget/git/pull/1231. It might involve nothing more than submitting those patches; they might be good enough already. (Alternatively, I can type "/submit" to send them in...if someone else agrees to respond to any feedback.)