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

Re: apply-mbox claiming corrupt patch.

From
Junio C Hamano <junkio@cox.net>
Date
Sep 27, 2006, 05:02 UTC
Message-ID
<7vu02tj41b.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060927024628.GA29182@redhat.com>
Dave Jones <davej@redhat.com> writes:
Show 9 quoted lines
> I tried to apply the mail below to my cpufreq.git tree on master.kernel.org,
> and got ..
>
> $ git-applymbox -k mbox
> 1 patch(es) to process.
>
> Applying '[CPUFREQ] Longhaul - Disable arbiter CLE266'
>
> fatal: corrupt patch at line 99

Like 99 (counting from where mailinfo splits proposed commit log message and the patch body which is '---' line) is the line after the closing brace "}" at the end of longhaul_cpu_init() function.

Show 12 quoted lines
> @@ -716,7 +739,7 @@ static int __init longhaul_cpu_init(stru
>  	return 0;
>  
>  err_acpi:
> -	printk(KERN_ERR PFX "No ACPI support for CPU frequency changes.\n");
> +	printk(KERN_ERR PFX "No ACPI support. No VT8601 or VT8623 northbridge. Aborting.\n");
>  	return -ENODEV;
>  }
>
>
> ----------------------------------------------------------------------
> Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e

The hunk claims to have 7 preimage lines and 7 postimage lines, so that empty line after the closing brace _is_ part of the hunk. And an empty context line is SP followed by LF. But the SP that should be at the beginning of that line does not exist.

In short, you have a corrupt patch.
Previous: Dave Jones
Message 4 of 4 in “apply-mbox claiming corrupt patch.”
  1. Dave JonesSep 27, 2006
  2. Len BrownSep 27, 2006
  3. Dave JonesSep 27, 2006
  4. Junio C HamanoSep 27, 2006

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.