MASON-INTEREST-L Archives

August 2010

MASON-INTEREST-L@LISTSERV.GMU.EDU
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Date:
Thu, 19 Aug 2010 14:56:40 -0400
Reply-To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Subject:
Re: Considering migrating to Google Code
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
<[log in to unmask]>
Content-Type:
text/plain; charset="us-ascii"
From:
John McManus <[log in to unmask]>
Parts/Attachments:
text/plain (21 lines) 
This would seem to open doors for complex, especially web-based programs. 

Would there be any implications regarding simple programs?

John

-----Original Message-----
From: MASON Multiagent Simulation Toolkit
[mailto:[log in to unmask]] On Behalf Of Sean Luke
Sent: Thursday, August 19, 2010 2:13 PM
To: [log in to unmask]
Subject: Considering migrating to Google Code

We've been given the green light by folks at Google to migrate MASON  
from java-dev to Google Code.  I am inclined to do so, not the least  
of which because it gives us the easiest path to upgrade from CVS to  
SVN.  Google Code also supports Mercurial, but I'm not sure that'd be  
of much benefit to us.  Opinions?

Sean

ATOM RSS1 RSS2