From: "streamlake@tiscali.it" <streamlake@tiscali.it>
To: git@vger.kernel.org
Subject: gitk error on cygwin
Date: Thu, 9 Apr 2009 09:29:14 +0200 (CEST) [thread overview]
Message-ID: <4019929.147451239262154071.JavaMail.defaultUser@defaultHost> (raw)
Hi,
While browsing revisions in gitk on a windows xp machine and cygwin
version (I tried both the packaged and a compiled one) I always find
tis error:
fatal: write failure on stdout: No such file or directory
fatal: write failure on stdout: No such file or directory
while
executing
"close $bdf"
(procedure "getblobdiffline" line 12)
invoked from within
"getblobdiffline file102f41f0
5978405b2bdf0c43c3b49427b0167eb31d433fe4"
("eval" body line 1)
invoked from within
"eval $script"
(procedure "dorunq" line 11)
invoked from within
"dorunq"
("after" script)
After this gitk
becomes unstable and doesn't show diffs,
Thanks,
Frank
Con Tutto Incluso chiami e navighi senza limiti e hai 4 mesi GRATIS.
L'attivazione del servizio è gratis e non paghi più Telecom!
L'offerta è valida solo se attivi entro il 09/04/09 http://abbonati.tiscali.it/promo/tuttoincluso/
reply other threads:[~2009-04-09 8:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4019929.147451239262154071.JavaMail.defaultUser@defaultHost \
--to=streamlake@tiscali.it \
--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.
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).