From: Philip Oakley <philipoakley@iee.email>
To: "Stewart, Tim" <Timothy.Stewart@Pearson.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: See Fault when running git diff
Date: Sat, 28 Mar 2020 17:08:46 +0000 [thread overview]
Message-ID: <11fa2daa-b301-6128-9f25-384a5ad7dc27@iee.email> (raw)
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)
prev parent reply other threads:[~2020-03-28 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 19:47 See Fault when running git diff Stewart, Tim
2020-03-28 17:08 ` Philip Oakley [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11fa2daa-b301-6128-9f25-384a5ad7dc27@iee.email \
--to=philipoakley@iee.email \
--cc=Timothy.Stewart@Pearson.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).