From: Eric McDonald <mcdonald@phy.cmich.edu>
To: xconq7 <xconq7@sources.redhat.com>
Cc: xconq-general@lists.sourceforge.net
Subject: Re: Multiple copies of messages
Date: Tue, 04 Jan 2005 19:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0501041402590.22788-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.53.0501041253110.7308@opal.ansuz.sooke.bc.ca>
Hi Matthew, welcome back,
On Tue, 4 Jan 2005 mskala@ansuz.sooke.bc.ca wrote:
> 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've been contemplating this same issue lately.
I'll look at the mailman settings for the lists tonight.
As far as CC'ing the Redhat list is concerned, I am willing to
quit doing that any time now. The Sourceforge listserv has shown
itself to just as reliable as the Redhat one, albeit with a
slower turnaround time. There are/were two reasons for CC'ing the
Redhat list: (1) As you mention, not everyone migrated. (2) This
whole jaunt over at Sourceforge was just intended to be a test to
see if SF.net could meet our needs. I believe that it has proven
reliable so far. My only complaints are that they are not
currently tracking CVS commits and adds, and that there is about 8
hour lag time between a CVS commit, and when it propagates to the
world-facing CVS pserver. However, I have no problems with CVS
checkout or commit failures. But, back to the mailings lists__, I
think Sourceforge has shown that it could be the "official" home
of Xconq. If Stan gives his stamp of approval to this, I will
forgo the 'xconq7' mailing list.
Stan, if you're reading this, can we make the official site of
Xconq be at Sourceforge? Also, you are invited to be a project
admin on the Sourceforge site; just let me know the SF user ID
that should be added to the project.
> Would it be possible to move the
> subscriber list from sources.redhat.com to sourceforge, to lessen the
> impact of closing the older list?
That is a possibility, though whoever has access to the Redhat
mailing list manager would have to arrange for this. Also, it
would probably be good to get a nod of general consent from those
"affected" by the move.
Eric
P.S. It may be wondered why SF has 5 mailing lists (general,
developers, hackers, players, and cvs), whereas
sources.redhat.com only has 3 ([main list], cvs, and announce). I
thought it might be nice to separate the general discussion from
the developer and hacker discussions so as not to scare off Xconq
newbies. The cross-posting problem did not seem to be a major
problem in my mind when I was first structuring the lists.
prev parent reply other threads:[~2005-01-04 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 17:53 mskala
2005-01-04 19:31 ` Eric McDonald [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=Pine.LNX.4.44.0501041402590.22788-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--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).