Move part of macports infrastructure to GitHub

[Mark Anderson]

Yeah, I actually like the idea of GitHub for the idea of pull requests. So
much so, I mirror the Macports on github, make my changes in branches and
make patches for SVN there. I'm certain we could save all the history we
needed. I've made this shift several times on a few projects.

I even have base in there, where I am working on my Perl CPAN runner
(another hot topic, I know), so we maybe won't need 87 Perls.

--Mark
_______________________
Mark E. Anderson <emer at emer.net>


On Sun, Mar 16, 2014 at 2:52 PM, <MK-MacPorts at techno.ms> wrote:

> On 16 Mar 2014, at 19:42 , Sean Farley <sean at macports.org> wrote:
> > I would suggest Mercurial.
>
> +1
>
> But, in order to avoid any flamewars: I'd be going for git as well, if it
> would win in an election. :-)
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140316/fae84c32/attachment.html>