[Swift-devel] Migrating to github

[Tim Armstrong]

I actually have a version of Swift/T up on github:
https://github.com/timarmstrong/swift-t

It was a minor pain to get it set up, but I have scripts now that I can run
to copy across changes from the SVN repo.

- Tim


On Tue, Feb 4, 2014 at 2:04 PM, Mihael Hategan <hategan at mcs.anl.gov> wrote:

> Interesting.
>
> Given that we are the only active committers to java cog at this point,
> I see no downside to making our own copy and merging it with swift.
>
> I also believe that the license allows this, but we need to check the
> details.
>
> Might seem a little backstabby towards Gregor, but I'm not sure how much
> he cares at this point. I can send him an email and explain that it
> would make it easier for us to do things this way. I suspect that a
> prominent "this project uses code developed by ..." would be a
> reasonable way to address the moral/ethical issues involved.
>
> Mihael
>
> On Tue, 2014-02-04 at 11:44 -0600, David Kelly wrote:
> > Right now we have two repos - cog on sourceforge, and Swift on
> > svn.ci.uchicago.edu.
> >
> > Sourceforge's SVN commit hooks are broken, so we do not get email updates
> > automatically from them when a change is made. Instead I rigged a cron
> job
> > that runs every 5 minutes, checks for changes, and emails them out. It's
> a
> > little ugly.
> >
> > Developers wanting to make contributions to Swift need a CI account. This
> > may discourage new developers from getting involved.
> >
> > Having two repos makes branching, tagging, and building more tedious than
> > it needs to be.
> >
> > This may need more discussion, but I would like to propose that starting
> > with 0.95, let's merge cog and Swift and move to github.
> > Right now we have two repos - cog on sourceforge, and Swift on
> > svn.ci.uchicago.edu.
> >
> >
> > Sourceforge's SVN commit hooks are broken, so we do not get email
> > updates automatically from them when a change is made. Instead I
> > rigged a cron job that runs every 5 minutes, checks for changes, and
> > emails them out. It's a little ugly.
> >
> >
> > Developers wanting to make contributions to Swift need a CI account.
> > This may discourage new developers from getting involved.
> >
> >
> > Having two repos makes branching, tagging, and building more tedious
> > than it needs to be.
> >
> >
> > This may need more discussion, but I would like to propose that
> > starting with 0.95, let's merge cog and Swift and move to github.
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20140204/480263be/attachment.html>