On Aug 19, 2016, at 10:24 PM, Lawrence Velázquez wrote: > Any documentation we write should be written specifically for developers > > 1. who are accustomed to using Subversion, and > 2. want to translate *their MacPorts workflow* to Git. > > We shouldn't expend effort rewriting a sloppier version of every generic > "this is how version control works" Git tutorial on the Web. There's quite > enough of that.
Maybe what we really need is documentation for MacPorts developers that just covers how to do whatever they need to do, using git. (I don't know if we had such a document for Subversion.) Things like... When first starting to contribute, fork the repo, clone the fork to your Mac; if you already have a fork, update it with the latest changes (how?). Create a branch for your changes. Make your changes in your text editor. Use "git diff" to see the changes. Use "git commit" to commit them. Use "git push" something to push them to GitHub. Submit a pull request on GitHub. When the pull request is accepted, delete your branch. At various step along the way, we could add "historical note" boxes showing how those step were done with Subversion. At some point in the future we'll probably want to remove the Subversion historical information, but still have the git instructions. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
