From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Adrian Ang <adrian.c.ang@gmail.com>,
Renato Akaboci <renato.akaboci@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: error opening
Date: Sat, 12 Sep 2015 11:56:52 +0200 [thread overview]
Message-ID: <ace58f6b47c9c7096f8f30a4472433e8@dscho.org> (raw)
In-Reply-To: <loom.20150911T232244-141@post.gmane.org>
Hi Adrian,
please note that Renato never got your mail (you should always use reply-to-all). I re-Cc:ed him, please do not forget to reply-to-all next time.
On 2015-09-11 23:33, Adrian Ang wrote:
> Renato Akaboci <renato.akaboci <at> gmail.com> writes:
>>
>> I´m in trouble just after installation of my Git for Windows.
>> I get a box with error saying:
>>
>> couldn´t read file "C:\Program
>> Files\Git\cmd\mingw64\libexec\git-core\git-gui": no such file or
>> directory
>
> I'm having the exact same problem.
Please see the corresponding ticket: https://github.com/git-for-windows/git/issues/376
In short: I will release an updated installer soon, with other fixes. In the meantime, as a work-around you could right-click on the Git GUI shortcut (you can right-click the icon in the Windows menu and open the file location to get there), select Properties... and change the Target: from
"C:\Program Files\Git\cmd\git-gui.exe"
to
"C:\Program Files\Git\cmd\git.exe" gui
It will open an ugly, unnecessary console until the next Git for Windows version is available, but at least it will work until then.
Out of curiosity: how did you go about finding the best place to report this bug?
Ciao,
Johannes
next prev parent reply other threads:[~2015-09-12 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 16:48 error opening "git gui" Renato Akaboci
2015-09-11 18:45 ` error opening Long
2015-09-11 21:33 ` Adrian Ang
2015-09-12 9:56 ` Johannes Schindelin [this message]
2015-09-12 16:17 ` Andy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ace58f6b47c9c7096f8f30a4472433e8@dscho.org \
--to=johannes.schindelin@gmx.de \
--cc=adrian.c.ang@gmail.com \
--cc=git@vger.kernel.org \
--cc=renato.akaboci@gmail.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.
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 NNTP newsgroup(s).