Moving to GitHub: Status Update, Action Required
larryv at macports.org
Fri Oct 21 19:47:07 PDT 2016
> On Oct 21, 2016, at 10:20 PM, Craig Treleaven <ctreleaven at macports.org> wrote:
> However, would it be possible to add a tangible example of updating
> a port to that page?
> I know a little bit about Subversion and less about Git. I would like
> to see a soup-to-nuts example of cloning the ports tree, updating
> a Portfile, maybe deleting an old patch and adding a new one, and
> getting the updated port into MacPorts (direct commit v. pull
> request). It would be helpful if one-time requirements (setting name
> and email address) were clearly separated from repetitive steps
> (pulling changes from master?). Otherwise, it is going to be a wee
> bit nerve-wracking the first few times...
This would be good.
> Also, is the consensus that a graphical user interface over git more
> likely to be harmful than helpful? The Tools section at the bottom of
> the page doesn’t give any kind of recommendation.
I don't know that there is any sort of consensus on that. Everyone has
their own preferences, and Git is almost absurdly flexible about
workflows. I don't think our documentation should recommend any
More information about the macports-dev