From: Ingo Molnar <mingo@elte.hu>
To: git@vger.kernel.org
Subject: [user confusion] git-config error messages
Date: Mon, 12 May 2008 16:16:37 +0200 [thread overview]
Message-ID: <20080512141636.GA29590@elte.hu> (raw)
ok, i thought i'd share this stupid little episode of user error.
I wanted to enable git-rerere:
$ git-config --add rerere.enabled true
could not lock config file
#
# Hm, do remember this option incorrectly? And what lock file?
#
$ git-config --add rerere.enabled=1
key does not contain a section: --add
#
# What section? What key?
#
$ git-config --add rerere.enabled=true
key does not contain a section: --add
#
# Huh? Ok, lets try strace:
#
$ strace -f git-config --add rerere.enabled true 2>&1 | grep \\.lock
open(".git/config.lock", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = -1 ENOENT (No such file or directory)
#
# Ah, stupid me! I forgot to cd into the Git repository and it tries to
# access .git. And i wanted the --global option anyway. So the Git
# error messages led me on the completely wrong path.
#
next reply other threads:[~2008-05-12 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 14:16 Ingo Molnar [this message]
2008-05-12 21:41 ` [PATCH] Improve reporting of errors in config file routines Alex Riesen
2008-05-12 22:10 ` Junio C Hamano
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=20080512141636.GA29590@elte.hu \
--to=mingo@elte.hu \
--cc=git@vger.kernel.org \
/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).