From: Lincoln Peters <sampln@sbcglobal.net>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7 <xconq7@sources.redhat.com>
Subject: Re: Xconq Mailing Lists - Please Read
Date: Fri, 08 Apr 2005 15:50:00 -0000 [thread overview]
Message-ID: <1112975421.29266.129.camel@localhost.localdomain> (raw)
In-Reply-To: <42568041.1030206@phy.cmich.edu>
On Fri, 2005-04-08 at 06:59 -0600, Eric McDonald wrote:
> > Or am I the only person who managed to not make the transition? Weird.
>
> The Sourceforge mailing lists have been mentioned on this list before,
> but, no, I don't think you're the only one who has not made the transition.
I noticed that the home page on RedHat's server makes no mention of the
move to the SourceForge site. In fact, it apparently has not been
updated since May 24 of last year. That could easily be a source of
confusion for a lot of people, especially as long as Google lists the
RedHat site at the top of the search results when someone does a search
for "Xconq" (Coop's website is listed second, and the SourceForge site
is listed eighth).
---
Lincoln Peters
<sampln@sbcglobal.net>
You are in a maze of little twisting passages, all different.
next prev parent reply other threads:[~2005-04-08 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 12:18 Recent Mac OS X Build? Bob Beaty
2005-04-08 12:39 ` Philip J. Hollenback
2005-04-08 12:59 ` Xconq Mailing Lists - Please Read Eric McDonald
2005-04-08 15:50 ` Lincoln Peters [this message]
2005-04-08 18:11 ` Eric McDonald
2005-04-09 5:46 ` Lincoln Peters
2005-04-09 15:04 ` Following Discussion Context Eric McDonald
2005-04-08 19:10 ` Xconq Mailing Lists - Please Read Stan Shebs
2005-04-09 1:59 ` Eric McDonald
2005-04-08 13:33 ` Recent Mac OS X Build? Bruno Boettcher
2005-04-08 12:45 ` Eric McDonald
2005-04-11 16:03 ` Robert Goulding
2005-04-11 16:57 ` 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=1112975421.29266.129.camel@localhost.localdomain \
--to=sampln@sbcglobal.net \
--cc=mcdonald@phy.cmich.edu \
--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).