git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	git@vger.kernel.org
Subject: [OT] Activision (Re: use binmode(STDOUT) in git-status)
Date: Tue, 29 Nov 2005 14:44:31 -0800	[thread overview]
Message-ID: <7vwtir846o.fsf_-_@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051129221221.GC3033@steel.home> (Alex Riesen's message of "Tue, 29 Nov 2005 23:12:21 +0100")

Alex Riesen <raa.lkml@gmail.com> writes:

> Johannes Schindelin, Mon, Nov 28, 2005 17:56:58 +0100:
>> > if you're running Cygwin, wouldn't Cygwin's Perl make a lot more sense?
>> 
>> I thought so, too, but I guess there's a reason that Activision's perl was 
>> used.
>
> the reason were incompatible scripts (notably, the ones expecting crlf).

I wonder why people keep saying Activision ;-).  Taken with my
use of frotz and nitfol in the examples [*1*], somebody might
confuse us with a group of old Infocom [*2*] fans.

[1] http://en.wikipedia.org/wiki/Nitfol
[2] http://web.mit.edu/6.933/www/Fall2000/infocom/

  reply	other threads:[~2005-11-29 22:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28  7:34 use binmode(STDOUT) in git-status Alex Riesen
2005-11-28 15:55 ` H. Peter Anvin
2005-11-28 16:02   ` Johannes Schindelin
2005-11-28 16:08     ` H. Peter Anvin
2005-11-28 16:56       ` Johannes Schindelin
2005-11-29 22:12         ` Alex Riesen
2005-11-29 22:44           ` Junio C Hamano [this message]
2005-11-29 23:56             ` [OT] Activision (Re: use binmode(STDOUT) in git-status) Johannes Schindelin
2005-11-28 18:31 ` use binmode(STDOUT) in git-status Junio C Hamano
2005-11-29 10:05   ` Tim O'Callaghan
2005-11-29 11:44     ` Johannes Schindelin

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=7vwtir846o.fsf_-_@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=raa.lkml@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).