public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: mskala@ansuz.sooke.bc.ca
To: xconq-general@lists.sourceforge.net, xconq7 <xconq7@sources.redhat.com>
Subject: Multiple copies of messages
Date: Tue, 04 Jan 2005 17:53:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.53.0501041253110.7308@opal.ansuz.sooke.bc.ca> (raw)

I wonder if there's a way we could either reduce the current cross-posting
of messages, or lessen its impact.  We have four discussion mailing lists
on SourceForge, as well as the one on sources.redhat.com.  Quite often a
given message will be relevant to two of the SourceForge lists, so it gets
crossposted to both of those, but then it'll also be crossposted to the
redhat.com list because lots of people haven't subscribed to the
SourceForge lists yet, and the lists are configured to encourage direct
CC:s of replies to the original poster, so if I've previously participated
in a discussion I'll probably be on the CC: list as well, and so the end
result is that I usually get three or four copies of every message.  I
have to manually skip the extra copies, and it seems quite likely that I
could miss seeing something important because I deleted it thinking it was
a duplicate of something else.

Is the CC:-to-original-poster thing really a good idea?  Do we still need
the sources.redhat.com mailing list?  Would it be possible to move the
subscriber list from sources.redhat.com to sourceforge, to lessen the
impact of closing the older list?  Is there a way to configure
SourceForge's mailing-list software to only send one copy of a given
message to one recipient, across mailing lists?
-- 
Matthew Skala
mskala@ansuz.sooke.bc.ca                    Embrace and defend.
http://ansuz.sooke.bc.ca/

             reply	other threads:[~2005-01-04 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-04 17:53 mskala [this message]
2005-01-04 19:31 ` Eric McDonald

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=Pine.LNX.4.53.0501041253110.7308@opal.ansuz.sooke.bc.ca \
    --to=mskala@ansuz.sooke.bc.ca \
    --cc=xconq-general@lists.sourceforge.net \
    --cc=xconq7@sources.redhat.com \
    /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).