From: Bart Schaefer <schaefer@brasslantern.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: A bug tracker (was: Re: [Bug] Unexpected process suspension)
Date: Wed, 20 May 2020 21:44:31 -0700 [thread overview]
Message-ID: <CAH+w=7YXXNXrZC=qsU4oK30z5zpK_V2MOagUeY3b3qdHhaX-Cw@mail.gmail.com> (raw)
In-Reply-To: <20200521033301.35393ae9@tarpaulin.shahaf.local2>
On Wed, May 20, 2020 at 8:33 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Rudi C wrote on Thu, 21 May 2020 03:02 +0430:
> > Github issue tracker is a lot better
> > than mailing lists, as things have a dichotomy of being open/closed, and
> > can be labeled. It is harder for issues to die a silent death there.
>
> I'm not opposed to adding a proper issue tracker, but github is not the
> only fish in the sea; it is one option among many.
Indeed, if we're going to continue hosting the git repository on
SourceForge, then reviving some kind of use of the bug tracker there
would seem to make more sense than github.
next prev parent reply other threads:[~2020-05-21 4:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 7:02 [Bug] Unexpected process suspension Rudi C
2020-05-12 11:48 ` Daniel Shahaf
2020-05-12 11:53 ` Roman Perepelitsa
2020-05-12 11:57 ` Daniel Shahaf
2020-05-12 12:05 ` Roman Perepelitsa
2020-05-12 13:31 ` Stephane Chazelas
2020-05-12 17:38 ` Bart Schaefer
2020-05-13 6:29 ` Stephane Chazelas
2020-05-20 22:32 ` Rudi C
2020-05-21 3:33 ` A bug tracker (was: Re: [Bug] Unexpected process suspension) Daniel Shahaf
2020-05-21 4:44 ` Bart Schaefer [this message]
2020-05-21 13:39 ` Oliver Kiddle
2020-05-21 16:46 ` Daniel Shahaf
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='CAH+w=7YXXNXrZC=qsU4oK30z5zpK_V2MOagUeY3b3qdHhaX-Cw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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).