Re: Git add claims path is ignored, but git check-ignore returns no results

2019-08-12 Thread geoffsimons


Hi Peff,

Thanks, I didn't think that would make any difference either, but changing the 
case resolved it! I'm now able to find the relevant line in the .gitignore file.

Regards,

Geoff

-Original Message-
From: Jeff King 
To: geoffsimons 
CC: git 
Sent: Mon, 12 Aug 2019 17:35
Subject: Re: Git add claims path is ignored, but git check-ignore returns no 
results

On Mon, Aug 12, 2019 at 04:24:59PM +, geoffsim...@aim.com wrote:


> I can’t find anything relevant in .git/info/exclude either, or any of
> the .gitignore files I could find.
> 
> git check-ignore 
> .\Source\UI\Website\LiveFeeds\Releases\IO\ReleasesSerializer.cs
> git add .\Source\ui\Website\LiveFeeds\Releases\io\ReleasesSerializer.cs
> The following paths are ignored by one of your .gitignore files:
> Source/ui/Website/LiveFeeds/Releases/io/ReleasesSerializer.cs
> Use -f if you really want to add them.
> 
> I get a similar result for adding files in that directory, or the
> parent directory (releases), but the grandparent directory (livefeeds)
> works fine.  Any ideas what might be causing this?


I notice that your "add" and "check-ignore" commands differ in the case
of "UI". I think both commands should work correctly when on a
case-insensitive filesystem (and a few checks I did after setting
core.ignorecase manually seem to confirm this).

But maybe try it with "ui" in the check-ignore command and see if that
changes anything?

Another thing I notice is that you're using Windows-style back-slashes
for the path separators (whereas internally in Git, everything is
front-slashes). AFAIK that's supposed to work everywhere on Windows, but
I wouldn't be surprised if there are corner cases where it doesn't. Does
switching to:

  git check-ignore 
./Source/ui/Website/LiveFeeds/Releases/IO/ReleasesSerializer.cs

help?

-Peff




Re: Git add claims path is ignored, but git check-ignore returns no results

2019-08-12 Thread Jeff King
On Mon, Aug 12, 2019 at 04:24:59PM +, geoffsim...@aim.com wrote:

> I can’t find anything relevant in .git/info/exclude either, or any of
> the .gitignore files I could find.
> 
> git check-ignore 
> .\Source\UI\Website\LiveFeeds\Releases\IO\ReleasesSerializer.cs
> git add .\Source\ui\Website\LiveFeeds\Releases\io\ReleasesSerializer.cs
> The following paths are ignored by one of your .gitignore files:
> Source/ui/Website/LiveFeeds/Releases/io/ReleasesSerializer.cs
> Use -f if you really want to add them.
> 
> I get a similar result for adding files in that directory, or the
> parent directory (releases), but the grandparent directory (livefeeds)
> works fine.  Any ideas what might be causing this?

I notice that your "add" and "check-ignore" commands differ in the case
of "UI". I think both commands should work correctly when on a
case-insensitive filesystem (and a few checks I did after setting
core.ignorecase manually seem to confirm this).

But maybe try it with "ui" in the check-ignore command and see if that
changes anything?

Another thing I notice is that you're using Windows-style back-slashes
for the path separators (whereas internally in Git, everything is
front-slashes). AFAIK that's supposed to work everywhere on Windows, but
I wouldn't be surprised if there are corner cases where it doesn't. Does
switching to:

  git check-ignore 
./Source/ui/Website/LiveFeeds/Releases/IO/ReleasesSerializer.cs

help?

-Peff


Git add claims path is ignored, but git check-ignore returns no results

2019-08-12 Thread geoffsimons
Hi,

I’m struggling with this.  Adding a renamed file to git claims that it is 
ignored, but git check-ignore returns no results.  
I can’t find anything relevant in .git/info/exclude either, or any of the 
.gitignore files I could find.

git check-ignore .\Source\UI\Website\LiveFeeds\Releases\IO\ReleasesSerializer.cs
git add .\Source\ui\Website\LiveFeeds\Releases\io\ReleasesSerializer.cs
The following paths are ignored by one of your .gitignore files:
Source/ui/Website/LiveFeeds/Releases/io/ReleasesSerializer.cs
Use -f if you really want to add them.

I get a similar result for adding files in that directory, or the parent 
directory (releases), but the grandparent directory (livefeeds) works fine.  
Any ideas what might be causing this?

Regards,

Geoff