On Sat, Aug 20, 2016 at 11:44 PM, Ian Wadham <iandw...@gmail.com> wrote:
> Fork the repo?? github expects you to do this, yes. I don't actually recommend it because keeping up to date with the original repo's a PITA (and *not* automated in any way. https://help.github.com/articles/syncing-a-fork/ is annoyingly manual). You lose the ability to maintain your clone with github's web interface, but that's not much of a loss really. (Or you can do their thing in reverse: clone the repo, add github as an additional upstream, create a new empty repo (not a fork) via their web interface, push to github periodically as a backup.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
