[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] admin: update NEWS
From: |
Jim Meyering |
Subject: |
[PATCH] admin: update NEWS |
Date: |
Thu, 07 May 2009 15:22:19 +0200 |
FYI,
>From 5aa7858385f7f6fe8c6f873ff1ba510b87288241 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Thu, 7 May 2009 15:17:53 +0200
Subject: [PATCH] admin: update NEWS
* NEWS (Bug fixes): Mention the date-related fixes.
(Portability): Mention the ACL-related fixes on *BSD.
---
NEWS | 21 ++++++++++++++++++++-
1 files changed, 20 insertions(+), 1 deletions(-)
diff --git a/NEWS b/NEWS
index e998d37..5ab1115 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]
--
1.6.3.195.gad81
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [PATCH] admin: update NEWS,
Jim Meyering <=