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

Re: [PATCH] Another config file parsing fix.

From
sean <seanlkml@sympatico.ca>
Date
May 6, 2006, 18:25 UTC
Message-ID
<BAYC1-PASMTP08FCAC8B8FB768ED1791F1AEAA0@CEZ.ICE>
In-Reply-To
<20060506141402.3909cb37.seanlkml@sympatico.ca>

On Sat, 6 May 2006 14:14:02 -0400 sean <seanlkml@sympatico.ca> wrote:

Show 10 quoted lines
> If the variable we need to store should go into a section
> that currently only has a single variable (not matching
> the one we're trying to insert), we will already be into
> the next section before we notice we've bypassed the correct
> location to insert the variable.
> 
> To handle this case we store the current location as soon
> as we find a variable matching the section of our new
> variable.
> 
    
Sorry.. this should really be amended to mention that it was Linus
who spotted the problem.
Sean
Next: sean
Message 1 of 3 in “Re: [PATCH] Another config file parsing fix.”
  1. seanMay 6, 2006
  2. t1300-repo-config: two new config parsing tests.sean, May 6, 2006
  3. Johannes SchindelinMay 6, 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.