From: "Shawn O. Pearce" <spearce@spearce.org>
To: Ray Lehtiniemi <rayl@mail.com>
Cc: git@vger.kernel.org
Subject: Re: problem viewing git.git with gitk on cygwin
Date: Mon, 16 Jul 2007 23:14:48 -0400 [thread overview]
Message-ID: <20070717031448.GI32566@spearce.org> (raw)
In-Reply-To: <200707161330.36907.rayl@mail.com>
Ray Lehtiniemi <rayl@mail.com> wrote:
> i'm seeing a problem with gitk on cygwin. if i try and view the history of
> git itself, it seems to stop at version 22dcbb. interestingly, the next
> commit 3ef378 has an embedded CTRL-Z character in the commit message.
>
> possible DOS EOF handling bug? or is there a repo setting i need to be
> tweaking?
>
> using git version 1.5.2.2, installed using the cygwin package setup tool.
Not Git's fault; Tcl on Cygwin honors EOF. Because nobody would
ever put that byte into a data stream. ;-)
Looks like gitk needs to add -eofchar {} to an fconfigure command
before it reads data from Git. Otherwise on Windows systems it
just stops reading. I better do the same to git-gui. *sigh*
--
Shawn.
prev parent reply other threads:[~2007-07-17 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 19:30 problem viewing git.git with gitk on cygwin Ray Lehtiniemi
2007-07-17 3:14 ` Shawn O. Pearce [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070717031448.GI32566@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=rayl@mail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.