Repository navigation
git node backport v8 does not work on macOS #421
Description
Activity
The line originates here and unfortunately it looks like you're right - the patch commands are similar on macOS and on Linux but there are some nontrivial option differences, one of which is the
--mergecommand.I think our best bet here is probably to move away from the
patchcommand and usegit applyto accomplish the same goal. The consequent difference unfortunately though is thatgit applywon't apply a given patch if you have other uncommitted changes in your code, & it also won't apply a patch that does not apply cleanly. The above linked code would therefore require some light restructuring to take those externalities into account.cc @targos for other thoughts!
I don't know what
patch --mergeleaves on the filesystem when there's a conflict, butgit apply -3(to do a three-way merge) worked for me 👍@dominykas what did
git apply -3leave?I vaguely remember that
git applydidn't always leave conflict markers, but maybe I'm wrong. And it's probably better to have something that work sometimes on all platforms than never on macOS
I got an error saying
Resolve merge conflicts and enter 'RESOLVED'- however there were no conflicts. The actual underlying failure waspatch: unrecognized option '--merge'- it seems thepatchon macOS does not have that option.I'm happy to research/PR whatever would be considered an acceptable fix?
Also not sure if there's a good way to detect conflicts vs other kinds of errors - the error message was rather misleading.