aboutsummaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorMathieu Arnold <mat@FreeBSD.org>2020-05-14 14:33:34 +0000
committerMathieu Arnold <mat@FreeBSD.org>2020-05-14 14:33:34 +0000
commitc671212915bf451f0b3636cb9ee5f152cef07428 (patch)
tree2557a15788e94600b2f0d7905e5684d2b39a8654 /CHANGES
parent8201a7ecc798aa0d8d27c278873ae8ac7d44525c (diff)
downloadports-c671212915bf451f0b3636cb9ee5f152cef07428.tar.gz
ports-c671212915bf451f0b3636cb9ee5f152cef07428.zip
Add PATCH_CONTINUE_ON_FAIL to allow patching to go through all the
patches even if one fail. This helps when upgrading ports with a large number of patches, like www/chromium where having to fix one patch, re-do the patching, fix the fallout, 800 times, is really painful. This fixes the first attempt at this which would make ports with multiple patches patching one file somewhat explode.
Notes
Notes: svn path=/head/; revision=535241
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES10
1 files changed, 10 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 5276e917be7c..6f6b1ec74470 100644
--- a/CHANGES
+++ b/CHANGES
@@ -10,6 +10,16 @@ in the release notes and/or placed into UPDATING.
All ports committers are allowed to commit to this file.
+20200514:
+AUTHOR: mat@FreeBSD.org
+
+ Add PATCH_CONTINUE_ON_FAIL to allow patching to go through all the patches
+ even if one fail.
+
+ This helps when upgrading ports with a large number of patches, like
+ www/chromium where having to fix one patch, re-do the patching, fix the
+ fallout, 800 times, is really painful.
+
20200414:
AUTHOR: bapt@FreeBSD.org