From: Christopher Faylor <cgf@redhat.com>
To: Robert Love <rml@tech9.net>
Cc: overseers@sources.redhat.com
Subject: Re: procps repository
Date: Sat, 01 Feb 2003 01:24:00 -0000 [thread overview]
Message-ID: <20030201012520.GA3981@redhat.com> (raw)
In-Reply-To: <1044056907.882.37.camel@phantasy>
On Fri, Jan 31, 2003 at 06:48:28PM -0500, Robert Love wrote:
>- First, the spam on the list is awful. Take a look at the archives for
>an example. It is measured in multiple-messages-per-day and it probably
>outranks legit email 10 to 1. That is an awful signal to noise ratio.
>I am on other Red Hat lists (libc-alpha, etc.) and they are not heavily
>spammed, so I assume the filter code is in place. Can a filter be
>installed, please?
AFAICT, the procps mailing list is not hosted at sources.redhat.com.
>- Second, the Reply-To header is forced to the list, and not the
>recipient. I think everyone agrees this is evil.
Can't help here, if we don't host the mailing list.
>- Third, the CVSWEB repository does not exist. Would it be possible to
>enable CVSWEB for procps?
I've added it.
>- Finally, the procps-bugs mailing list can be removed in favor of all
>messages going to procps-list.
Can't help here, either, unfortunately.
The CVS repository is on sources.redhat.com but no one has even checked
in a project web page. I wonder if it has actually moved elsewhere or
never fully moved to sources.redhat.com.
cgf
next prev parent reply other threads:[~2003-02-01 1:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 23:48 Robert Love
2003-02-01 0:23 ` Jason Molenda
2003-02-01 1:24 ` Christopher Faylor [this message]
2003-02-01 1:37 ` Robert Love
2003-02-01 1:46 ` Christopher Faylor
2003-02-01 1:51 ` Robert Love
2003-02-01 2:02 ` Christopher Faylor
2003-02-01 2:19 ` Robert Love
2003-02-01 2:22 ` Christopher Faylor
2003-02-01 2:30 ` Robert Love
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=20030201012520.GA3981@redhat.com \
--to=cgf@redhat.com \
--cc=overseers@sources.redhat.com \
--cc=rml@tech9.net \
/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 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 read-only IMAP folder(s) and NNTP newsgroup(s).