Closed cavaliercoder closed 7 years ago
What is the best way to go about this? git merge, git rebase, git rebase and then git merge the rebase and master, or git revert?
I'm not sure the best plan. My working plan was to:
Ok, the second to last option.
I cloned your fork, performed a pull on the dmidecode master branch to the latest and greatest commit, performed some merge conflict resolutions, created unified diff files, and then packed them all in to this one zip file. I haven't tested it yet. I accepted all suggestions from AUTHORS (with slight modifications) and dmidecode.c since these were the only 2 issues that required a personal touch.
Thanks for putting some time into. It's really critical that we do test the side-effects of each merge-conflict before proceeding with this.
Ok. I had errors during make and I fix them. They work on my system running Mac OS High Sierra version 3. Here is the patch. I'm including the 5 errors as a screenshot. dmidecode.c.diff.zip
I've rebased onto the dmidecode-3.1
branch from https://git.savannah.nongnu.org/git/dmidecode.git. Homebrew package upgraded to v3.1.
dmidecode v3.1 was recently released and should be merged down.