Document incompatible changes in 'format-time-string'

* etc/NEWS: Mention the incompatible change in the interpretation
of the 3rd argument to 'format-time-string'.  (Bug#21943)
This commit is contained in:
Eli Zaretskii 2016-04-02 16:23:05 +03:00
parent 7228eb805d
commit 104221731e

View file

@ -1771,6 +1771,11 @@ rule. The affected functions are 'current-time-string',
function 'encode-time', which already accepted a simple time zone rule function 'encode-time', which already accepted a simple time zone rule
argument, has been extended to accept all the new forms. argument, has been extended to accept all the new forms.
*** Incompatible change in the third argument of 'format-time-string'.
Previously, any non-nil argument was interpreted as a UTC time zone.
This is no longer true; packages that want UTC time zone should pass t
as the third argument.
*** Time-related functions now consistently accept numbers *** Time-related functions now consistently accept numbers
(representing seconds since the epoch) and nil (representing the (representing seconds since the epoch) and nil (representing the
current time) as well as the usual list-of-integer representation. current time) as well as the usual list-of-integer representation.