n C projects which reference 4 different versions of a device SDK -
15.2. There is no public upstream repo for the SDK - it is released as a
zip file. We need to patch the SDK to work for our particular needs, and would like to minimize copy-paste code sharing.
I would like to put the SDK versions in a
git repo to share the current state of our patches between our
n projects. My plan is to put all SDK versions as branches from a (mostly) empty
Is this a common best practice? If not, what is the common best practice for tracking local changes to unversioned 3rd party code, with dependencies on several releases?