#3 Keep patches more closely to original code for easier review.
Opened 4 years ago by darkdragon001. Modified 4 years ago
https://github.com/darkdragon-001/netpbm-rpm.git master  into  master

No commits found

no initial comment
  • Keep whitespace as is
  • Apply upstream code changes to patches where applicable (e.g. outsourcing code into separate function)
  • Fix to actually run the python3 executable

To compare the changes, I recommend applying the patches to the source code and commit it in a (temporary) branch. Then apply the new set of patches on the original code and compare via git diff -w --ignore-blank-lines BRANCH.

Metadata