<div dir="ltr">Yeah, I agree with Ivan, the big deal is Github. Git is great, but hg offers a lot of the same stuff. As to Ryan's objections, I too had those same objections after working with SVN and CVS for almost 2 decades. But once I switched, I wondered why I hadn't switched earlier. I'm sure those of us in the community would be more than happy to help move things over, I know I would. I've been wanting to get more and more involved for a while. And I know Github pretty well. I also use Github Enterprise at work. <div>
<div><br></div><div>Not for nothing, but that search turned up roughly 22 pages of personal Macports repos. (alhtough a few referenced "Macports sucks" which I don't like, but eh. It was more positive than negative.</div>
<div><br></div><div>Mark</div><div><br></div><div><br></div><div><br></div><div><br></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 3:13 PM, Ivan Larionov <span dir="ltr"><<a href="mailto:xeron.oskom@gmail.com" target="_blank">xeron.oskom@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Actually main thing here isn’t git, but github. It’s interface and features<br>take contribution process to the next level. It’s so easy — just fork, commit<br>and send pull request.<br><br>
I understand that someone could like mercurial more and we have bitbucket,<br>but actually, I see people use github more and like it.<div><div><div><div class=""><br><div>
<div style="text-align:-webkit-auto;text-indent:0px;word-wrap:break-word"><div style="word-wrap:break-word">--</div><div style="word-wrap:break-word">With best regards, Ivan Larionov.</div></div>
</div>
<br></div><div class=""><div><div>On 16 марта 2014 г., at 22:42, Sean Farley <<a href="mailto:sean@macports.org" target="_blank">sean@macports.org</a>> wrote:</div><br><blockquote type="cite"><div style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<br>Ivan Larionov <<a href="mailto:xeron.oskom@gmail.com" target="_blank">xeron.oskom@gmail.com</a>> writes:<br><br><blockquote type="cite">I want to start this discussion mainly about ports tree, but actually base and some other stuff could use github and infra around it as well. I understand this is not so easy and may be you already discussed it and may be already decided not to do, but there are huge pros:<br>
<br>* git >> svn<br>* pull requests are awesome! No need to poke around with patch files attached to tickets<br>* nice UI, tools and infra around<br><br>which will result in more pros:<br><br>* people will look at macports more positively<br>
* and will contribute more!<br><br>Actually I see lot of people keeping their local ports at github: <a href="https://github.com/search?q=macports&type=Repositories&ref=searchresults" target="_blank">https://github.com/search?q=macports&type=Repositories&ref=searchresults</a><br>
<br>What do you think?<br></blockquote><br>I know this is a hot topic but I will try to avoid any flame wars.<br><br>If MacPorts really wants to switch to distributed version control, then<br>I would suggest Mercurial. I have experimented with using Mercurial for<br>
the MacPorts repo and found that the mercurial UI is much, much more<br>consistent than git coming from Subversion.<br><br>I've actually maintained a repo with merges, tags, and branches<br>correctly merged in here:<br>
<br><a href="https://smf.io/macports" target="_blank">https://smf.io/macports</a></div></blockquote></div><br></div></div></div></div></div><br>_______________________________________________<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>
<br></blockquote></div><br></div>