From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5490 invoked by alias); 21 Nov 2004 10:44:16 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 5474 invoked from network); 21 Nov 2004 10:44:09 -0000 Received: from unknown (HELO rwcrmhc12.comcast.net) (216.148.227.85) by sourceware.org with SMTP; 21 Nov 2004 10:44:09 -0000 Received: from [192.168.181.128] (c-67-176-41-158.client.comcast.net[67.176.41.158]) by comcast.net (rwcrmhc12) with ESMTP id <2004112110440801400a8tqle>; Sun, 21 Nov 2004 10:44:08 +0000 Message-ID: <41A0716C.9040505@phy.cmich.edu> Date: Mon, 22 Nov 2004 01:26:00 -0000 From: Eric McDonald User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) MIME-Version: 1.0 To: cstevens@gencom.us CC: mskala@ansuz.sooke.bc.ca, xconq7@sources.redhat.com Subject: Xconq @ Sourceforge (was Re: Grid To Hex Conversion) References: <200411120207.23320.cstevens@gencom.us> In-Reply-To: <200411120207.23320.cstevens@gencom.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg01423.txt.bz2 D. Cooper Stevenson wrote: >>I was also hoping that we'd have an official CVS again by the time I get a >>chance to work on image mapping, since the current pattern of getting >>updates as source tarballs makes it difficult for me to make modifications >>if my modifications will require more development time than the time >>between tarballs (hard to merge in new updates - that's part of the >>problem CVS is supposed to solve). > > > I hope we see this happen on SourceForge or Savannah. As you know, others have > asked for this. Everything is now in place at Sourceforge. (The project home page could use some cosmetics perhaps, but that it is nothing important.) Instructions on access to the CVS repository: http://sourceforge.net/cvs/?group_id=124062 CVS browser: http://cvs.sourceforge.net/viewcvs.py/xconq/xconq/ Mailing lists: http://sourceforge.net/mail/?group_id=124062 Bug tracker: http://sourceforge.net/tracker/?group_id=124062&atid=698372 Feature request tracker (note that Elijah has already been busy there :-)): http://sourceforge.net/tracker/?group_id=124062&atid=698375 Patch tracker: http://sourceforge.net/tracker/?group_id=124062&atid=698374 File releases: http://sourceforge.net/project/showfiles.php?group_id=124062 Project summary page: http://sourceforge.net/projects/xconq/ Fora are presently being handled by Xconq.org (thanks Coop): http://www.xconq.org/modules.php?name=Forums FYI, Eric P.S. Like Stan, I have already experienced some problems with the Sourceforge CVS servers. Import went fine, but the imported module did not become available via pserver to the outside world until about 9 hours later. I hope this was just a fluke and does not represent what we can expect from SF. ("Inside" pserver access from the SF shell machine was fine from the get go, as was SSH ext access from the outside world.)