NEW/RELEASE-NOTES: add items for portage-2.1.10

2 files changed, 18 insertions, 0 deletions

diff --git a/NEWS b/NEWS
index b0e04c140..44e95e095 100644
--- a/NEWS
+++ b/NEWS
@@ -9,10 +9,19 @@ portage-2.2
 * Add support for FEATURES=preserve-libs which preserves libraries when the
   sonames change during upgrade or downgrade, and the @preserved-rebuild
   package set which rebuilds consumers of preserved libraries.
+
+portage-2.1.10
+-------------
 * Improve handling of repositories/overlays for cases in which the same ebuild
   is provided by multiple repositories but with different masking status, and
   support for repository constraints on atoms (atom::repo) in configuration
   files.
+* Add emerge --rebuild-if-* options that trigger rebuilds of reverse
+  dependencies when packages are rebuilt or updated. Related --rebuild-exclude
+  and --rebuild-ignore options can be used to avoid rebuilds for specific
+  packages.
+* Add emerge --reinstall-atoms, --useoldpkg-atoms, and --usepkg-exclude options
+  which can be used to alter selection rules for specific packages.
 
 portage-2.1.9.27
 -------------
diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index e04b198b5..582bbb511 100644
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -20,6 +20,15 @@ portage-2.2
   /var/lib/portage/world, has been extended to include nested sets that may
   be listed /var/lib/portage/world_sets.
 
+portage-2.1.10
+==================================
+* The emerge --autounmask option is now enabled by default. The
+  --autounmask-write option can be used to have config changes automatically
+  written to the appropriate files (repecting --ask and CONFIG_PROTECT). If
+  --autounmask behavior is not desired as the default behavior, then it can
+  be disabled by adding --autounmask=n to the EMERGE_DEFAULT_OPTS variable in
+  make.conf. Refer to the emerge(1) man page for more information.
+
 portage-2.1.9
 ==================================
 * The emerge "world" set now includes separate "selected" and "system" sets,