summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorJim Meyering <meyering@redhat.com>2009-05-07 15:17:53 +0200
committerJim Meyering <meyering@redhat.com>2009-05-07 15:20:56 +0200
commit5aa7858385f7f6fe8c6f873ff1ba510b87288241 (patch)
treea4543a6d28808c485780b39f72459a2382e83b02 /NEWS
parenta6c9dd74d8083b27ca8db78791b9d6e7ba6d4478 (diff)
downloadcoreutils-5aa7858385f7f6fe8c6f873ff1ba510b87288241.tar.xz
admin: update NEWS
* NEWS (Bug fixes): Mention the date-related fixes. (Portability): Mention the ACL-related fixes on *BSD.
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS21
1 files changed, 20 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index e998d37b8..5ab111598 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,25 @@
GNU coreutils NEWS -*- outline -*-
-* Noteworthy changes in release ?.? (????-??-??) [?]
+* Noteworthy changes in release 7.4 (2009-05-07) [stable]
+
+** Bug fixes
+
+ date -d 'next mon', when run on a Monday, now prints the date
+ 7 days in the future rather than the current day. Same for any other
+ day-of-the-week name, when run on that same day of the week.
+ [This bug appears to have been present in "the beginning". ]
+
+ date -d tuesday, when run on a Tuesday -- using date built from the 7.3
+ release tarball, not from git -- would print the date 7 days in the future.
+ Now, it works properly and prints the current date. That was due to
+ human error (including not-committed changes in a release tarball)
+ and the fact that there is no check to detect when the gnulib/ git
+ submodule is dirty.
+
+** Portability
+
+ There have been some ACL-related portability fixes for *BSD,
+ inherited from gnulib.
* Noteworthy changes in release 7.3 (2009-05-01) [stable]