From: Adam Spiers <adam@spiers.net>
To: zsh-workers@sunsite.auc.dk
Subject: Re: List of unresolved issues (update)
Date: Mon, 1 May 2000 10:09:06 +0100 [thread overview]
Message-ID: <20000501100906.A17293@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <1000501052127.ZM8590@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Mon, May 01, 2000 at 05:21:27AM +0000
Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> Too bad, I want to collect them together somewhere. (I suppose I could
> file them as bugs on sourceforge ... do people find that bug tracker to
> be worthwhile?)
Yes, I think it's worthwhile. If bugs/bug lists are only posted to
the list, unless someone (you in this case) is good enough to
regularly keep track of and post outstanding bugs, they are very hard
to spot in the archive. If they're all in the bug tracker it's easy
for someone with a bit of free time (hah! as if...) to pick something
to work on.
The sourceforge bug tracker seems perfectly adequate to me, but if
there's a problem with it I've missed, we could always stuff your list
in Etc/BUGS. Or if we decide to use the bug tracker as the definitive
list, we should certainly mention it in Etc/BUGS.
next prev parent reply other threads:[~2000-05-01 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-12 6:14 List of unresolved issues Bart Schaefer
2000-04-12 15:56 ` Andrej Borsenkow
2000-04-12 20:55 ` Peter Stephenson
2000-04-13 0:26 ` Bart Schaefer
2000-04-13 8:56 ` Peter Stephenson
2000-04-13 14:10 ` PATCH: local exports Peter Stephenson
2000-04-13 15:42 ` Bart Schaefer
2000-04-13 17:54 ` PATCH: " Peter Stephenson
2000-05-01 5:21 ` List of unresolved issues (update) Bart Schaefer
2000-05-01 9:09 ` Adam Spiers [this message]
2000-05-02 9:50 ` Peter Stephenson
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=20000501100906.A17293@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.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).