On Fri, 23 Sep 2016, Clemens Lang wrote: > On Fri, Sep 23, 2016 at 01:08:38PM -0500, Ryan Schmidt wrote: > > Something I did not see discussed on this page was that after you > > fork, and before you start making changes, you should create a branch > > specific to the work you are doing. > > I didn't include this because it's not how I normally work. I usually > only create branches for larger changes. I wouldn't be opposed to > include it, but I'm probably not the best person to write these docs.
I always work that way so that I can keep branches inherited from upstream "pristine", i.e. fast-forwardable. That's less of an issue for someone with direct commit access, though even there, working in a branch and merging separately reduces the collision window for pushes. Fred Wright _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
