From: "Michał Kiedrowicz" <michal.kiedrowicz@gmail.com>
To: Erik Faye-Lund <kusmabite@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git config: cygwin git version 1.6.1.2 does not deletes empty sections
Date: Wed, 6 May 2009 22:43:27 +0200 [thread overview]
Message-ID: <20090506224327.23c69a06@gmail.com> (raw)
In-Reply-To: <40aa078e0905061108o21830f07xfb9d5c185c93fda6@mail.gmail.com>
Erik Faye-Lund <kusmabite@googlemail.com> wrote:
> On Wed, May 6, 2009 at 6:04 PM, Constantine Plotnikov
> <constantine.plotnikov@gmail.com> wrote:
> > The bug is also confirmed on MSYS git version 1.6.2.2.1669.g7eaf8.
>
> The same issue is present in git 1.6.2.1 on Linux. Not that I'm too
> sure it's really a bug, though ;)
>
Happens also in master (v1.6.3-rc4-29-g8146f19). IMO this is because
git_parse_file() reports only *variables*, not *sections* and
store_aux() doesn't find empty section.
--
Michał Kiedrowicz
prev parent reply other threads:[~2009-05-06 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 15:50 [BUG] git config: cygwin git version 1.6.1.2 does not deletes empty sections Constantine Plotnikov
2009-05-06 16:04 ` Constantine Plotnikov
2009-05-06 18:08 ` Erik Faye-Lund
2009-05-06 20:43 ` Michał Kiedrowicz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090506224327.23c69a06@gmail.com \
--to=michal.kiedrowicz@gmail.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).