git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alan Blotz <work@blotz.org>
To: git@vger.kernel.org
Subject: git difftool: No such file or directory
Date: Wed, 30 Jun 2021 11:38:21 +0200	[thread overview]
Message-ID: <176caa21-0232-9f21-7a8d-af136754e354@blotz.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2: git-bugreport-2021-06-30-1117.txt --]
[-- Type: text/plain, Size: 1136 bytes --]

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

mkdir broken-diff
cd broken-diff
git init
mkdir dir1
mkdir dir2
touch dir1/orig
cd dir2/
ln -s ../dir1/orig sym
cd ..
git add dir*
git ci -m "init"
git checkout -b b
git rm dir2/sym 
git ci -m "remove"
git difftool -d master HEAD

What did you expect to happen? (Expected behavior)

git difftool shall compare both branches.

What happened instead? (Actual behavior)

git difftool prints an error:

fatal: could not open '/tmp/git-difftool.l4UM7e/left/dir2/sym' for writing: No such file or directory

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.31.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.12.12-300.fc34.x86_64 #1 SMP Fri Jun 18 14:30:51 UTC 2021 x86_64
compiler info: gnuc: 11.0
libc info: glibc: 2.33
$SHELL (typically, interactive shell): /bin/bash


[Enabled Hooks]

             reply	other threads:[~2021-06-30  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  9:38 Alan Blotz [this message]
2021-07-01  0:35 ` git difftool: No such file or directory Đoàn Trần Công Danh
2021-08-30  0:32   ` David Aguilar

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=176caa21-0232-9f21-7a8d-af136754e354@blotz.org \
    --to=work@blotz.org \
    --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).