One approach is to merge the changes with another branch, but before merging, delete the content that is specific to the development.
First get the changes without binding them to git merge --no-ff --no-commit dev
.
Remove development-specific changes, either by editing the affected files, or git add
them, or git reset HEAD
affected files, and then git add --patch
the parts you want.
Then copy the merge. The advantage of performing a merger is that future mergers will be painless. Since development-specific commits are considered merged, future merges not related to specific parts can be performed using a simple git merge dev
. Thus, you can unlimitedly maintain a separate branch with its own configuration, while at the same time seamlessly merging with the changes in the leading branch.
source share