all: $(DEB)
@echo $(DEB)
-.PHONY: update-subtree deb upload distclean clean dinstall
-
-update-subtree:
- git subtree fetch $(UPSTREAM) master
- @printf "\nSubtree fetched, to merge in changes use something like:\n\n"\
- "\tgit subtree pull -P src --squash $(UPSTREAM) master\n"
+.PHONY: deb upload distclean clean dinstall
buildir: $(BUILDDIR)
$(BUILDDIR):
We're using git's subtree functionality, which is basically just a convenience wrapper around the
age old subtree merge strategy.
+The initial addition was done with the following command:
+```
+git subtree add -P src --squash https://salsa.debian.org/debian/ifupdown.git 0.8.36
+```
+
## Subtree Rules
* We squash update commits to avoid making the git log explode here, one can always checkout the
> will still make sense. But if this isn't important to you, it’s not necessary. git
> subtree will simply leave out the non-library-related parts of the commit when it
> splits it out into the subproject later.
+
+## Pull in New Version
+
+Use something like the followign command (adapt the refspec at the end) to pull
+and merge in a new upstream revision:
+
+```
+git subtree pull -P src --squash https://salsa.debian.org/debian/ifupdown.git 0.8.X
+```
+
+Handle merge conflicts and ensure that the *build* post/pre rm scripts don't do anything that would
+interfere with switching to ifupdown2 or purging this package later.