git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3] builtin/apply: handle parse_binary() failure

From
Christian Couder <christian.couder@gmail.com>
Date
Apr 1, 2016, 19:31 UTC
Message-ID
<CAP8UFD0RCECwy4DXM0PHe+K-XTiCbtur0dEhk6Z37wCKLDwfKQ@mail.gmail.com>
In-Reply-To
<xmqqvb41i705.fsf@gitster.mtv.corp.google.com>
On Fri, Apr 1, 2016 at 1:16 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 11 quoted lines
> Christian Couder <christian.couder@gmail.com> writes:
>>
>> It looks like this patch is not in pu. Maybe it has fallen through the cracks?
>
> Yup, it indeed was ignored (giving priority to work towards 2.8
> during the freeze) and then was forgotten.
>
> My comment on the first one that exited mentions "your follow-up
> patch", but I cannot quite tell which one, as there was no threading
> in your original patches.  Does this change need to come before
> something else that I already have?

No, I think by "your follow-up patch" you meant the other one that had also been forgotten and that I also replied to, that is:

[PATCH] builtin/apply: free patch when parse_chunk() fails
I had first sent both of them at around the same time.

Thanks, Christian.

Previous: Junio C Hamano
Message 4 of 4 in “builtin/apply: handle parse_binary() failure”
  1. builtin/apply: handle parse_binary() failureChristian Couder, Mar 18, 2016
  2. Christian CouderMar 31, 2016
  3. Junio C HamanoApr 1, 2016
  4. Christian CouderApr 1, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.