From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mark Phillips <mark.phil@samsung.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: BUG Report: v12.0.0 "git difftool -d" fails with "fatal: cannot create directory at '': No such file or directory"
Date: Thu, 2 Mar 2017 15:26:13 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703021523360.3767@virtualbox> (raw)
In-Reply-To: <f2a8495f22854a749e615fb642d5655d@CAMSVWEXC02.scsc.local>
Hi Mark,
On Thu, 2 Mar 2017, Mark Phillips wrote:
> I am building git from source using gcc 4.8.5 on 64 bit linux.
>
> I am sorry the log info is not very helpful, please tell me how to get
> more information about what is going wrong and I will collect the info
> for you!
Well, you could provide a Minimal, Complete and Verifiable Example
(http://stackoverflow.com/help/mcve): most likely, the error depends on
particular features of your current HEAD, or environment variables.
Because i do *not* get that error if I run `git difftool -d HEAD~`.
So it is not so much about collecting info as about distilling your use
case into an example that allows other developers to reproduce the
problem, and subsequently fix it.
Ciao,
Johannes
prev parent reply other threads:[~2017-03-02 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170302105511eucas1p2c40bbbb719c8fb15cc7a6cb9424a92e4@eucas1p2.samsung.com>
2017-03-02 10:55 ` BUG Report: v12.0.0 "git difftool -d" fails with "fatal: cannot create directory at '': No such file or directory" Mark Phillips
2017-03-02 14:26 ` Johannes Schindelin [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=alpine.DEB.2.20.1703021523360.3767@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mark.phil@samsung.com \
/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).