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

Re: [BUG] git config: cygwin git version 1.6.1.2 does not deletes empty sections

From
CPConstantine Plotnikov <constantine.plotnikov@gmail.com>
Date
May 6, 2009, 16:04 UTC
Message-ID
<85647ef50905060904w49879c57r4a5773a487f09c85@mail.gmail.com>
In-Reply-To
<85647ef50905060850t2e6c2051jfa6d3596b680cc74@mail.gmail.com>
The bug is also confirmed on MSYS git version 1.6.2.2.1669.g7eaf8.
Constantine

On Wed, May 6, 2009 at 7:50 PM, Constantine Plotnikov <constantine.plotnikov@gmail.com> wrote:

Show 33 quoted lines
> I have encountered a bug related to git config in cygwin git version 1.6.1.2
>
> The git config --unset might leave an empty section when the last
> property is deleted. But consequent "git config key value" does not
> uses this empty section. So the following script leaves a sequence of
> empty sections "[a]". Looks like a disk space leak to me.
>
> git config a.b a
> git config --unset a.b
> git config a.b a
> git config --unset a.b
> git config a.b a
> git config --unset a.b
> git config a.b a
> git config --unset a.b
>
> The resulting .git/config file:
>
> [core]
>        repositoryformatversion = 0
>        filemode = true
>        bare = false
>        logallrefupdates = true
>        ignorecase = true
> [a]
> [a]
> [a]
> [a]
>
> Was this bug fixed in later versions?
>
> Constantine
>
Previous: Constantine PlotnikovNext: Erik Faye-Lund
Message 2 of 4 in “[BUG] git config: cygwin git version 1.6.1.2 does not deletes empty sections”
  1. Constantine PlotnikovMay 6, 2009
  2. Constantine PlotnikovMay 6, 2009
  3. Erik Faye-LundMay 6, 2009
  4. Michał KiedrowiczMay 6, 2009

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.