From: Peter Oberndorfer <kumbayo84@arcor.de>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git config problem with strange config files
Date: Tue, 1 Jan 2008 15:25:48 +0100 [thread overview]
Message-ID: <200801011525.48148.kumbayo84@arcor.de> (raw)
In-Reply-To: <20080101061734.GA15453@coredump.intra.peff.net>
On Dienstag 01 Januar 2008, Jeff King wrote:
> On Mon, Dec 31, 2007 at 06:47:41PM +0100, Peter Oberndorfer wrote:
>
> > In case of a strange .git/config file "git config key value" can
> > create a bogus config entry, where one old value is wrong and the new
> > value resides in the wrong section until the config file is fixed up
> > by hand
>
> This patch fixes the test case you gave.
>
> Junio, even though such a config file should be rare, I think this is
> v1.5.4 material. But there is one tricky thing which I will point out in
> a followup mail.
>
Thank you for the patch
I would also guess this is relative rare, but IIRC somebody posted a patch to
handle a bogus config with a better message,
and the breakage example in the mail looked similar to mine.
How i came up with this bogus config is relative simple.
I wanted to add a new remote so i copied the already existing remote and
branch sections down to the last line and somehow also added a trailing tab.
Then i did a stg init which uses git repo-config to add its
stackformatversion = 2 setting
Greetings Peter
prev parent reply other threads:[~2008-01-01 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 17:47 git config problem with strange config files Peter Oberndorfer
2008-01-01 6:17 ` Jeff King
2008-01-01 6:23 ` Jeff King
2008-01-01 19:57 ` Junio C Hamano
2008-01-01 14:25 ` Peter Oberndorfer [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=200801011525.48148.kumbayo84@arcor.de \
--to=kumbayo84@arcor.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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