Setting `true` as the default for GIT_ICASE_PATHSPECS_ENVIRONMENT, when git is
built on a Windows system, solves the bug.
diff --git a/pathspec.c b/pathspec.c
index 12c2b322b3..906cf24e3e 100644
--- a/pathspec.c
+++ b/pathspec.c
@@ -237,7 +237,11 @@ static
Hi Guiseppe,
On 07/02/2019 19:41, Johannes Schindelin wrote:
Hi Giuseppe,
On Wed, 6 Feb 2019, Giuseppe Crinò wrote:
I wanted to have a look at the bug, and I can correctly reproduce it using
version 2.20.1.windows.1.
Thank you for having a look.
The root cause of the issues will most prob
On Fri, Feb 08, 2019 at 04:18:23PM +0100, Giuseppe Crinò wrote:
> OK, I successfully built git on Windows (thanks Johannes!) and I'm now able
> to run it.
>
> As of 9f16cdd I can successfully reproduce the bug.
>
> Interestingly enough, I can reproduce the bug even for /usr/bin/git running
> insi
Hi Giuseppe,
On Wed, 6 Feb 2019, Giuseppe Crinò wrote:
> I wanted to have a look at the bug, and I can correctly reproduce it using
> version 2.20.1.windows.1.
>
> To start to even think of fixing this bug I need to build the source for
> Windows, but I got lost on how to do that.
Does this h
I wanted to have a look at the bug, and I can correctly reproduce it using
version 2.20.1.windows.1.
To start to even think of fixing this bug I need to build the source for
Windows, but I got lost on how to do that.
Is it correct that I should cross-compile from a POSIX system (GNU/Linux),
us
On Fri, Feb 01, 2019 at 10:02:50AM +0200, Angelo Melonas wrote:
> Hi Torsten,
>
> Thank you so much for getting back to me.
>
> Unfortunately, I believe there is a misunderstanding, as I may have
> explained what I found to be a possible bug incorrectly.
> The file that is originally added (and the
Hi Torsten,
Thank you so much for getting back to me.
Unfortunately, I believe there is a misunderstanding, as I may have
explained what I found to be a possible bug incorrectly.
The file that is originally added (and then later modified) is never
renamed or moved.
As you will see below, when a u
On Thu, Jan 31, 2019 at 09:29:28AM +0200, Angelo Melonas wrote:
> Just to clarify, I made a mistake above. Instead of "untracked", I
> meant "unstaged".
> I apologise for the confusion.
>
> On Thu, Jan 31, 2019 at 9:01 AM Angelo Melonas
> wrote:
> >
> > Good day,
> >
> > I found a potential bug i
Just to clarify, I made a mistake above. Instead of "untracked", I
meant "unstaged".
I apologise for the confusion.
On Thu, Jan 31, 2019 at 9:01 AM Angelo Melonas wrote:
>
> Good day,
>
> I found a potential bug in Git for Windows. The bug can be reproduced
> as follows:
>
> 1. Modify a file so t
Good day,
I found a potential bug in Git for Windows. The bug can be reproduced
as follows:
1. Modify a file so that it shows up as "untracked" when executing the
"git status" command.
2. Attempt to "git add" the file, but change the case of a single
letter. The command executes but no warning or
10 matches
Mail list logo