From: Jeff King <peff@peff.net>
To: Moez Bouhlel <bmoez.j@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git ignores /~/.config/git/
Date: Wed, 14 Jan 2015 16:07:52 -0500 [thread overview]
Message-ID: <20150114210751.GD1155@peff.net> (raw)
In-Reply-To: <20150114193307.GA2592@lejenome.me>
On Wed, Jan 14, 2015 at 07:33:07PM +0000, Moez Bouhlel wrote:
> git exludes /~/.config/git/ from the matching list.
>
> ~ is the name of a dir on the root of git working tree and not my user home dir.
I'm not quite sure what you mean by "matching list". Do you mean that
the path is not listed as untracked in "git status"?
Are there any files inside the directory? Git will not mention empty
directories, as tracks only file content, not directories.
Beyond that, I cannot reproduce:
$ git init
$ mkdir -p '~/.config/git'
$ git status -s
Lack of output is expected, since there are no files. Now:
$ echo content >'~/.config/git/foo'
$ git status -s
?? ~/
$ git status -s -uall
?? ~/.config/git/foo
This is on Linux. Are you by any chance using Git for Windows? I wonder
if the recent chances to short-names like "foo~1" could have affected
this.
-Peff
prev parent reply other threads:[~2015-01-14 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 19:33 git ignores /~/.config/git/ Moez Bouhlel
2015-01-14 21:07 ` Jeff King [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=20150114210751.GD1155@peff.net \
--to=peff@peff.net \
--cc=bmoez.j@gmail.com \
--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).