From: Vinnie Shelton <shelton@icd.teradyne.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Bogus tempfile names in beta18
Date: Wed, 22 May 1996 13:38:19 -0400 [thread overview]
Message-ID: <9605221738.AA20352@spacely.afive> (raw)
In-Reply-To: hzoli's message of Wed, 22 May 1996 18:06:15 +0200. <199605221606.SAA29528@bolyai.cs.elte.hu>
In message <199605221606.SAA29528@bolyai.cs.elte.hu>, Zoltan Hidvegi wrote:
>Did you notice that these filenames are different?
Oops. Sorry about that. The first time I ran the test, I did it under
beta17, and then when I ran my test script under beta18, I just did
a visual inspection on the filenames.
My apologies,
vin
next prev parent reply other threads:[~1996-05-22 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-22 15:09 Vinnie Shelton
1996-05-22 16:06 ` Zoltan Hidvegi
1996-05-22 17:38 ` Vinnie Shelton [this message]
1996-05-22 16:18 ` Mark Borges
1996-05-22 16:21 ` Mark Borges
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=9605221738.AA20352@spacely.afive \
--to=shelton@icd.teradyne.com \
--cc=acs@world.std.com \
--cc=hzoli@cs.elte.hu \
--cc=zsh-workers@math.gatech.edu \
/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://git.vuxu.org/mirror/zsh/
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).