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 16:08:22 -0400
Reply-To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Content-Transfer-Encoding:
7bit
Subject:
From:
Mike Little <[log in to unmask]>
Content-Type:
text/plain; charset=ISO-8859-1
In-Reply-To:
Organization:
Telcordia Technologies, Applied Research Labs
MIME-Version:
1.0
Parts/Attachments:
text/plain (20 lines)
Sean -
  We've used Mercurial with much success - chosen primarily because
we have multiple sites that periodically update to each other (e.g. we
do not have direct network connectivity). I don't have any experience
with SVN so can't comment regarding pros/cons between the two.
  Besides a different source code management platform and a more
public hosting server, any other motivations for relocation?

-Mike

Sean Luke wrote:
> 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