From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Peter Stephenson" <pws@csr.com>,
"Zsh hackers list" <zsh-workers@sunsite.dk>
Subject: RE: Latest cvs hangs in completion tests
Date: Fri, 15 Jun 2001 16:20:41 +0400 [thread overview]
Message-ID: <003801c0f595$97e7b190$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <Tc0a88d015428448ca0@mailsweeper01.cambridgesiliconradio.com>
>
> That's the basis of it. I was just getting there. The following seems to
> do the trick. The tests now run, are then any more potential problems?
>
Are you going to commit it?
bor@itsrm2% cd /to/b/zTAB
_setup:5: read-only variable: *
-andrej
prev parent reply other threads:[~2001-06-15 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 20:48 Peter Whaite
2001-06-15 9:52 ` Peter Stephenson
2001-06-15 9:59 ` Peter Stephenson
2001-06-15 10:05 ` Bart Schaefer
2001-06-15 10:25 ` Peter Stephenson
2001-06-15 12:20 ` Andrej Borsenkow [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='003801c0f595$97e7b190$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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).