> On Aug 20, 2016, at 11:55 PM, Brandon Allbery <[email protected]> wrote: > >> On Sat, Aug 20, 2016 at 11:44 PM, Ian Wadham <[email protected]> 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.
Don't you also lose the ability to submit pull requests to the original repository? I don't see how noncommitters would contribute without having their own forks. I guess they could continue sending patches to Trac, but we are hoping to move away from that. vq _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
