<div dir="ltr">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. <div>
<br><div>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.</div></div></div><div class="gmail_extra"><br clear="all"><div>—Mark<br>_______________________<br>
Mark E. Anderson <<a href="mailto:emer@emer.net" target="_blank">emer@emer.net</a>><br></div>
<br><br><div class="gmail_quote">On Sun, Mar 16, 2014 at 2:52 PM, <span dir="ltr"><<a href="mailto:MK-MacPorts@techno.ms" target="_blank">MK-MacPorts@techno.ms</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 16 Mar 2014, at 19:42 , Sean Farley <<a href="mailto:sean@macports.org">sean@macports.org</a>> wrote:<br>
> I would suggest Mercurial.<br>
<br>
+1<br>
<br>
But, in order to avoid any flamewars: I’d be going for git as well, if it would win in an election. :-)<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
macports-dev mailing list<br>
<a href="mailto:macports-dev@lists.macosforge.org">macports-dev@lists.macosforge.org</a><br>
<a href="https://lists.macosforge.org/mailman/listinfo/macports-dev" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-dev</a><br>
</div></div></blockquote></div><br></div>