From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] RFC: remove/restart bugs.parisc-linux.org
Date: Tue, 22 Apr 2003 12:05:09 -0400 [thread overview]
Message-ID: <20030422160509.GG26986@systemhalted> (raw)
In-Reply-To: <20030422071920.GO25257@tausq.org>
> We have a bts setup at bugs.parisc-linux.org, but it hasn't been touched
> for a very long time, and the only purpose it seems to serve nowadays is
> to archive spam. Should we just remove it? There are a lot of items
> there that remain "TODO" items... but perhaps a better way to keep
> track of those is to put a todo list in cvs (we already have one for the
> kernel... we can start one for userspace stuff too), and we can link to
> it via viewcvs from the web page.
I'm all for:
a. Removing the BTS.
b. Adding userspace cvs-based TODO list.
c.
prev parent reply other threads:[~2003-04-22 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 7:19 [parisc-linux] RFC: remove/restart bugs.parisc-linux.org Randolph Chung
2003-04-22 16:05 ` Carlos O'Donell [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=20030422160509.GG26986@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.