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

Re: [PATCH] commit: Remove backward goto in read_craft_line()

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 1, 2010, 20:19 UTC
Message-ID
<7vaakputxs.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20101201194441.GB27347@burratino>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 10 quoted lines
>> @@ -155,6 +151,11 @@ struct commit_graft *read_graft_line(char *buf, int len)
>>  			goto bad_graft_data;
>>  	}
>>  	return graft;
>> +
>> +bad_graft_data:
>> +	error("bad graft data: %s", buf);
>
> A space before the "bad_graft_data:" label would improve future
> diff --show-c-function output.
Hmm, I actually do not think we encourage that (nor we should).
    $ git grep -e '^ [a-z0-9]*:' -- '*.c' | wc -l
    23
    $ git grep -e '^[a-z0-9]*:' -- '*.c' | wc -l
    42

If "--show-c-function" output is the problem, perhaps we should know a bit better about what C function header looks like?

Previous: Jonathan NiederNext: Jonathan Nieder
Message 3 of 8 in “commit: Remove backward goto in read_craft_line()”
  1. commit: Remove backward goto in read_craft_line()Ralf Thielow, Dec 1, 2010
  2. Jonathan NiederDec 1, 2010
  3. Junio C HamanoDec 1, 2010
  4. Jonathan NiederDec 1, 2010
  5. Ralf ThielowDec 1, 2010
  6. Trivial patches (Re: [PATCH] commit: Remove backward goto in read_craft_line())Jonathan Nieder, Dec 1, 2010
  7. Junio C HamanoDec 1, 2010
  8. Ralf ThielowDec 1, 2010

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.