So since MacPorts is moving to git, and from what I saw in the "how to use git" docs you mentioned, you apparently want people to work with patchsets rebased onto the current head from upstream.
As I was thinking about that, I realized that you lose your history of the patchset in the process. The Git mailing list pointed me to these resources, that I thought I'd pass up to you. 1. git-series: track changes to a patch series over time " Debian package maintenance tends to have this exact family of problems: maintaining a set of patches to upstream code, rebasing those patches on new upstream versions, reorganizing/refining/adding/dropping patches, having individual patches merged upstream, and backporting changes *from* upstream." https://lists.debian.org/debian-devel-announce/2016/10/msg00004.html 2. Stacked git -- looks like a similar system, tracking a "stack of patches". https://stgit.org/ 3. A discussion looking at git-series vs stacked git: https://lists.debian.org/debian-devel/2016/08/msg00220.html --- Entertaining minecraft videos http://YouTube.com/keybounce _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
