From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh workers mailing list <zsh-workers@math.gatech.edu>
Subject: Re: Miscellaneous buglettes
Date: 07 Sep 1999 03:55:56 +0900 [thread overview]
Message-ID: <rsqk8q327k3.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: Adam Spiers's message of "Sun, 5 Sep 1999 22:45:40 +0100"
In article <19990905224540.A7557@thelonious.new.ox.ac.uk>,
Adam Spiers <adam@thelonious.new.ox.ac.uk> writes:
> I've been building a list of bugs (I think) I've discovered with
> 3.1.6. Ideally I would like to have checked they haven't already been
> fixed before reporting them, but you guys work so damn fast that I
> can't keep up with all your patches. I don't think I've seen any of
> these mentioned recently, but to this end if someone gets around to
> providing anonymous CVS, I'd be enormously grateful. In the meantime,
> realistically the best I can manage is patches to pws-2.
Personally, I'm tracking latest zsh by cvs. And it can be accessed by
anonymous cvs.
Try `:pserver:anonymous@crane.jaist.ac.jp:/projects/zsh'.
The password is empty string and module name is `zsh'.
The main trunc should be latest zsh.
P.S.
Please keep the following description of zsh-development-guide:
Please make sure the filenames in the diff header
are relative to the top-level directory of the zsh distribution; for
example, it should say "Src/init.c" rather than "init.c" or
"zsh/Src/init.c".
Your diff headers like
--- zsh-3.1.6-4/Doc/Zsh/compsys.yo Mon Sep 6 13:15:29 1999
+++ zsh-3.1.6-adam/Doc/Zsh/compsys.yo Mon Sep 6 14:14:31 1999
confuse my script to apply patches semi-automatically.
(In this case, `patch -p0' cannot find `compsys.yo'.)
--
Tanaka Akira
next prev parent reply other threads:[~1999-09-06 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-05 21:45 Adam Spiers
1999-09-06 9:01 ` Peter Stephenson
1999-09-06 10:27 ` Adam Spiers
1999-09-06 18:55 ` Tanaka Akira [this message]
1999-09-06 9:34 Sven Wischnowsky
1999-09-06 9:39 Sven Wischnowsky
1999-09-06 9:55 Sven Wischnowsky
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=rsqk8q327k3.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--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).