From: "Torsten Bögershausen" <tboegi@web.de>
To: Adrian Kappel <atkappel@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Bug Report] [includeIf] does not parse case insensitive -> case sensitive symlink gitdir
Date: Fri, 27 Oct 2017 17:33:36 +0200 [thread overview]
Message-ID: <20171027153336.GA26626@tor.lan> (raw)
In-Reply-To: <CAEm1wifEZ5CXH7N_cCJpXQN-1dWBRZ1OQ=bJH-X=kR15Bg0Sdw@mail.gmail.com>
On Fri, Oct 27, 2017 at 09:55:58AM -0400, Adrian Kappel wrote:
> Hello all, not sure if the issue I've come across is a known bug or
> addressable, but wanted to report it just in-case.
Thanks for the detailed description - my question is inline
>
>
> ** Summary
> ------------------------------------------------------------------
> Using the [includeIf] configuration statement with a symlink'd gitdir
> will not work if the symlink is on a case insensitive volume and the
> location it references is on a case sensitive volume.
>
> ** Steps to reproduce
> ------------------------------------------------------------------
> 1. Create symlink (case insensitive -> case sensitive):
> /Users/usera/dev -> /Volumes/CaseSensitive/dev
> 2. Create two files: .gitignore and .gitignore-work, both stored in
> /Users/usera/
>
> .gitconfig
> -------------
> [user]
> name = First Last
>
> [includeIf "gitdir:~/dev/work"]
> path = .gitconfig-work
>
> .gitconfig-work
> --------------------
> [user]
> email = email@address.com
>
> 3. cd into a subfolder of ~/dev/work that has been git initialized.
> Let's say ~/dev/work/repo
> 4. Run git config --includes user.email
> 5. See that nothing is output from the command
> 6. Update the [includeIf] statement in .gitconfig to be the real
> location i.e. "gitdir:/Volumes/CaseSensitive/dev/work/repo"
Didn't you set it up pointing do the real location ?
That is what is written above:
> 1. Create symlink (case insensitive -> case sensitive):
> /Users/usera/dev -> /Volumes/CaseSensitive/dev
(I suspect that people use something like this:
/Users/usera/dev -> /Volumes/casesensitive/dev
And in this case it would be the file system which says
casesensitive != CaseSensitive and Git can't do much about it)
> 7. Rerun the command from [4]
> 8. See that email@address.com is output from the command
>
> ** Other variations that were not tested
> ------------------------------------------------------------------
> - symlink on case sensitive volume referencing a location on a case
> insensitive volume
>
> ** Environment Information
> ------------------------------------------------------------------
> git --version: 2.14.1
> OS: macOS Sierra 10.12.6
>
>
> If a fix is not feasible or likely to be implemented, I would
> recommend that we update the git site's documentation to reflect this
> gotcha. After verification of course.
>
> Best,
> Adrian Kappel
> akappel <https://github.com/akappel/>
prev parent reply other threads:[~2017-10-27 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 13:55 [Bug Report] [includeIf] does not parse case insensitive -> case sensitive symlink gitdir Adrian Kappel
2017-10-27 15:33 ` Torsten Bögershausen [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=20171027153336.GA26626@tor.lan \
--to=tboegi@web.de \
--cc=atkappel@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).