[gentoo-commits] proj/portage:master commit in: /

["Brian Dolbec" <brian.dolbec@gmail.com>]

commit:     dbf539165c4ff26b08c86ef8c25111a8c354910a
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Sun Jan  5 23:13:15 2014 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Sun Jan  5 23:15:41 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=dbf53916

Update the release notes for a release.

---
 RELEASE-NOTES | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index ec6cecd..8a35b55 100644
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -1,6 +1,15 @@
 Release Notes; upgrade information mainly.
 Features/major bugfixes are listed in NEWS
 
+portage-2.2.8
+==================================
+* Bug Fixes:
+    - Bug 488972 - sys-apps/portage-2.2.7:
+      "egencache --update --rsync" does not create metadata/timestamp.chk
+    - For a complete list of bug fixes, changes, See the Changelog installed at
+      /usr/share/doc/portage-2.2.8/ChangeLog.bz2
+
+
 portage-2.2
 ==================================
 
@@ -124,7 +133,7 @@ portage-2.1.6
 * The python namespace for portage has been sanitized, all portage related code
   is now contained within the portage namespace. External script should be
   updated accordingly, though links exist for backward compability.
-* -* support in package.keywords was changed as it was inconsistent with 
+* -* support in package.keywords was changed as it was inconsistent with
   ACCEPT_KEYWORDS behavior (also see
   http://dev.gentoo.org/~genone/docs/KEYWORDS.stupid).
   Previously having -* in package.keywords matched packages with KEYWORDS="-*",
@@ -230,7 +239,7 @@ portage-2.1.1
 
 * emerge --search doesn't use regular expressions now anymore by default, so
   emerge --search dvd+rw-tools now works as expected. Regular expressions can be enabled
-  by prefixing the search string with %. 
+  by prefixing the search string with %.
 * emerge --depclean algorithm is much safer than the old one.
 * emerge --newuse detects changes in IUSE that previously went undetected.
 
@@ -243,9 +252,9 @@ portage-2.1
   by the name of --alphabetical.  Adding the option to EMERGE_DEFAULT_OPTS
   in make.conf will restore the old behaviour permanently.
 * The deprecated --inject has been removed, use /etc/portage/profile/package.provided
-* The deprecated --upgradeonly has been removed, use /etc/portage/package.* 
+* The deprecated --upgradeonly has been removed, use /etc/portage/package.*
   instead.
-* 'emerge sync' has been deprecated, use 'emerge --sync' instead (same 
+* 'emerge sync' has been deprecated, use 'emerge --sync' instead (same
   for other actions)
 * Tools that call emerge should override the EMERGE_DEFAULT_OPTS environment
   variable or use the emerge --ignore-default-opts option.
@@ -254,6 +263,6 @@ portage-2.1
 * autouse (use.defaults) has been deprecated by specifying USE_ORDER in make.defaults
   Users may still turn this back on by specifying USE_ORDER="env:pkg:conf:auto:defaults"
   in make.conf.  Interested in figuring out what use flags were turned off?  Check out
-  /usr/portage/profiles/base/use.defaults and other use.defaults files that correspond 
+  /usr/portage/profiles/base/use.defaults and other use.defaults files that correspond
   to your profile.