Re: Unresolved issues #2

From: Jakub Narebski <jnareb@gmail.com>
Date: May 7, 2006, 00:41 UTC
Message-ID: <e3jfmh$1vc$1@sea.gmane.org>
In-Reply-To: <7vvesirh0q.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

> It might make sense to rewrite it to parse and read the existing
> configuration as a whole, do necessary manupulations on the
> parsed internal representation in-core, and write the result out
> from scratch.

Or perhaps do git repo-config read and change config file in two passes: read and build some kind of index (beginning of section, end of section/last variable in section, number of elements in section), then in second pass add some information if needed.

-- 
Jakub Narebski
Warsaw, Poland

$ 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.