From: Philip Oakley Date: Sat, 28 Mar 2020 17:08:46 GMT Subject: Re: See Fault when running git diff Message-ID: <11fa2daa-b301-6128-9f25-384a5ad7dc27@iee.email> In-Reply-To: <771f0c5de3874158acdeb18003ac62495F73D361-1387-42DA-B582-725ADA24BB21@pearson.com> Hi Tim, On 15/01/2020 19:47, Stewart, Tim wrote: > Steps to reproduce: > > > Start a rebase operation that results in one or more conflicts in one or more of the repository’s sub-directories. > List the conflicts with the following command: git diff --name-only --diff-filter=U –relative > Identify one of the conflicts that is in a subdirectory. > cd to that directory > Run the same command again: git diff --name-only --diff-filter=U –relative > Receive segmentation fault error.  I would have expected to see a list of files relative to the current directory. > The following commands work just fine in the subdirectory you cd’ed to (I introduced spacing to make which arguments are present or absent more clear): > git diff --name-only --diff-filter=U > git diff                        --diff-filter=U –relative > > >   > It appears that the –diff-filter=U argument is not required to induce the seg fault making the minimal failing case: ‘git diff --name-only –relative’ when run from a subdirectory. Is this still present in the recent V2.26.0? -- Philip, (catching up on old emails)