From: Jorge <griffin@gmx.es>
To: git@vger.kernel.org
Subject: Bug: .gitconfig folder
Date: Wed, 27 May 2015 15:29:11 +0200 [thread overview]
Message-ID: <5565C6A7.60007@gmx.es> (raw)
If you have a folder named ~/.gitconfig instead of a file with that
name, when you try to run some global config editing command it will
fail with a wrong error message:
"fatal: Out of memory? mmap failed: No such device"
You can reproduce it:
$rm ~/.gitconfig
$mkdir ~/.gitconfig
$ls -la ~
...
drwxr-xr-x 24 hit hit 4096 may 4 12:30 .gimp-2.8
drwxr-xr-x 2 hit hit 4096 may 27 15:26 .gitconfig
drwxr-xr-x 6 hit hit 4096 may 27 14:01 github
...
$git config --global user.name foo
fatal: Out of memory? mmap failed: No such device
$git config --global core.editor "vim"
fatal: Out of memory? mmap failed: No such device
next reply other threads:[~2015-05-27 13:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 13:29 Jorge [this message]
2015-05-27 20:30 ` Bug: .gitconfig folder Junio C Hamano
2015-05-27 22:18 ` Jeff King
2015-05-27 22:24 ` Stefan Beller
2015-05-28 6:13 ` Jeff King
2015-05-27 22:38 ` Junio C Hamano
2015-05-28 7:51 ` Jeff King
2015-05-28 7:54 ` [PATCH 1/4] read-cache.c: drop PROT_WRITE from mmap of index Jeff King
2015-05-28 7:54 ` [PATCH 2/4] config.c: fix mmap leak when writing config Jeff King
2015-06-30 14:34 ` [PATCH] config.c: fix writing config files on Windows network shares Karsten Blees
2015-06-30 14:46 ` Torsten Bögershausen
2015-06-30 16:01 ` Jeff King
2015-06-30 14:52 ` Johannes Schindelin
2015-06-30 16:00 ` Jeff King
2015-05-28 7:56 ` [PATCH 3/4] config.c: avoid xmmap error messages Jeff King
2015-05-28 8:03 ` [PATCH 4/4] config.c: rewrite ENODEV into EISDIR when mmap fails Jeff King
2015-05-28 17:11 ` Junio C Hamano
2015-05-28 20:44 ` Jeff King
2015-05-28 21:11 ` Junio C Hamano
2015-05-28 17:06 ` Bug: .gitconfig folder 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=5565C6A7.60007@gmx.es \
--to=griffin@gmx.es \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.