public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
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: Sat, 09 Apr 2005 05:46:00 -0000	[thread overview]
Message-ID: <1113025525.6600.6.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0504081404260.11376-100000@leon.phy.cmich.edu>

On Fri, 2005-04-08 at 14:11 -0400, Eric McDonald wrote: 
> If you want to see it updated, then either I need to 
> have assurances that Hans will not be having any more accidents 
> (allegedly) that clobber my CVS commits, or you will need to get 
> someone else to do it. Talk to Stan maybe....

I don't think that it's necessary to keep it up-to-date, but I think
that if it's not going to be updated, then it needs to say that the
Xconq project has moved to SourceForge.  Otherwise, I'm pretty sure that
the confusion will continue.

> 
> >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).
> 
> Actually, it varies a fair amount. One of the reasons that the 
> old site comes out higher is because it is cross-referenced in 
> more categories in various directories. In the dmoz open 
> directory, it is linked to one additional category. I could 
> counter this by simply removing the primary reference to it, but I 
> think that would be overstepping the bounds of my editorial 
> discretion on dmoz....

If there is a link to the SourceForge site given on the old site, I'm
not sure that this will be a problem.  Eventually, other sites that
reference the Xconq project will (hopefully) figure out that we've moved
the project and update their links, thus making the new site appear at
the top of the results when Googl'ed, and finally allowing us to take
the old site down.

Or so we can hope...

---
Lincoln Peters
<sampln@sbcglobal.net>

One of the most overlooked advantages to computers is...  If they do
foul up, there's no law against whacking them around a little.
		-- Joe Martin

  reply	other threads:[~2005-04-09  5:46 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
2005-04-08 18:11       ` Eric McDonald
2005-04-09  5:46         ` Lincoln Peters [this message]
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=1113025525.6600.6.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).