Re: Goodbye Mac OS Forge, hello GitHub

2016-08-19 Thread Lawrence Velázquez
> On Aug 19, 2016, at 8:18 PM, Ryan Schmidt wrote: > > And our new buildbot automated build system announced earlier this month is > being hosted by me on my hardware, outside of Apple, and will just need > minor changes to monitor GitHub instead of Subversion. FYI I've made some progress on thi

Re: How to use git

2016-08-19 Thread Lawrence Velázquez
Hi Ian, > On Aug 20, 2016, at 1:47 AM, Ian Wadham wrote: > > I don't know if this applies to Macports, but KDE did a lot of splitting of > SVN > "module" repositories into individual project repositories on git. For > example, > the KDE Games module on SVN went from one repository to about 40

Re: How to use git

2016-08-19 Thread Ian Wadham
Hi Lawrence, On 20/08/2016, at 1:24 PM, Lawrence Velázquez wrote: >> On Aug 19, 2016, at 11:16 PM, Ian Wadham wrote: >> >> Qt and KDE moved from svn to git a while back. IIRC it was quite an effort >> for a >> few individuals to port all the repositories across and preserve all the >> history

Re: How to use git

2016-08-19 Thread Lawrence Velázquez
> On Aug 19, 2016, at 11:20 PM, Brandon Allbery wrote: > >> On Fri, Aug 19, 2016 at 11:16 PM, Ian Wadham wrote: >> >> Qt and KDE moved from svn to git a while back. IIRC it was quite an effort >> for a >> few individuals to port all the repositories across and preserve all the >> history. >>

Re: How to use git

2016-08-19 Thread Lawrence Velázquez
> On Aug 19, 2016, at 11:16 PM, Ian Wadham wrote: > > Qt and KDE moved from svn to git a while back. IIRC it was quite an effort > for a > few individuals to port all the repositories across and preserve all the > history. > They had to write lots of scripts and check all the results. I hope

Re: How to use git

2016-08-19 Thread Brandon Allbery
On Fri, Aug 19, 2016 at 11:16 PM, Ian Wadham wrote: > Qt and KDE moved from svn to git a while back. IIRC it was quite an > effort for a > few individuals to port all the repositories across and preserve all the > history. > They had to write lots of scripts and check all the results. I hope it

Re: How to use git

2016-08-19 Thread Ian Wadham
On 20/08/2016, at 11:49 AM, Mark Anderson wrote: > I use git (and Github Enterprise) in my day to day work. I can help out. > > Another good (free (as in beer)) client is SourceTree > https://www.sourcetreeapp.com/ Qt and KDE moved from svn to git a while back. IIRC it was quite an effort fo

Re: How to use git

2016-08-19 Thread Mark Anderson
I use git (and Github Enterprise) in my day to day work. I can help out. Another good (free (as in beer)) client is SourceTree https://www.sourcetreeapp.com/ —Mark ___ Mark E. Anderson On Fri, Aug 19, 2016 at 8:19 PM, Ryan Schmidt wrote: > Here are some resources GitHub re

Re: Goodbye Mac OS Forge, hello GitHub

2016-08-19 Thread Mark Anderson
Yeah, no one wants Github to be the new SF. Thankfully, git helps there, we can pick up and move anytime. Also, it's a bit less once size fits all thing than SF. SF had everything. Github is more focused. The lack of ads and the pay to play system makes me feel better about it. —Mark _

Re: Goodbye Mac OS Forge, hello GitHub

2016-08-19 Thread Kevin Walzer
On 8/19/16 8:18 PM, Ryan Schmidt wrote: Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the decade since Mac OS Forge was created, collaborative software development platforms like GitHub and BitBucket have become very popular and successful, and when I was hired as Mac OS F

Re: Goodbye Mac OS Forge, hello GitHub

2016-08-19 Thread Ryan Schmidt
On Aug 19, 2016, at 7:28 PM, C. R. Oldham wrote: > On August 19, 2016 at 6:19:06 PM, Ryan Schmidt wrote: > >> I'm pleased to announce that MacPorts will be moving its source code to >> GitHub. > This is fantastic and phenomenal. > > Does this mean that updates to ports can be submitted via GitH

Re: Goodbye Mac OS Forge, hello GitHub

2016-08-19 Thread Mark Anderson
This is super exciting. I can ditch my weird github workflow and have my own proper fork. And I agree, github issues really are terrible, glad to see we're sticking with trac. —Mark ___ Mark E. Anderson On Fri, Aug 19, 2016 at 8:28 PM, C. R. Oldham wrote: > > > > On August

Re: Goodbye Mac OS Forge, hello GitHub

2016-08-19 Thread C. R. Oldham
On August 19, 2016 at 6:19:06 PM, Ryan Schmidt (ryandes...@macports.org) wrote: I'm pleased to announce that MacPorts will be moving its source code to GitHub. This is fantastic and phenomenal. Does this mean that updates to ports can be submitted via GitHub Pull Request? --cro ___

Re: Goodbye Mac OS Forge, hello GitHub

2016-08-19 Thread Jake Petroules
Hey Ryan, This is AWESOME news! Been hoping to hear this for a while now, and it will definitely make my qbs port maintainership a bit easier. :D Looking forward to to the move and a big welcome to the next generation of MacPorts! > On Aug 19, 2016, at 5:18 PM, Ryan Schmidt wrote: > > I'm pl

How to use git

2016-08-19 Thread Ryan Schmidt
Here are some resources GitHub recommends for learning git: https://help.github.com/articles/good-resources-for-learning-git-and-github/ When MacPorts moves to GitHub, committers will need to stop using their existing Subversion working copies and get a fresh copy of the code from GitHub. There w

Subversion log editing and other unfinished work

2016-08-19 Thread Ryan Schmidt
In preparation for moving MacPorts source code to git, we will be disabling the ability to edit Subversion revision properties, including commit messages (the svn:log property). Once we move to git, editing commit messages won't be permitted anymore either. While it's technically possible to do so

Goodbye Mac OS Forge, hello GitHub

2016-08-19 Thread Ryan Schmidt
I'm pleased to announce that MacPorts will be moving its source code to GitHub. The exact date for the move has not yet been set; this message is just to let you know that these changes are coming soon. Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the decade since Mac OS F