From: Robert Pluim <rpluim@gmail.com>
To: Stephen Gildea <stepheng+emacs@gildea.com>
Cc: 32931@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#32931: time-stamp-format: offer numeric time zones too
Date: Thu, 07 Nov 2019 10:02:06 +0100 [thread overview]
Message-ID: <m2lfssvz3l.fsf@gmail.com> (raw)
In-Reply-To: <26918.1573058926@quatro> (Stephen Gildea's message of "Wed, 06 Nov 2019 08:48:46 -0800")
>>>>> On Wed, 06 Nov 2019 08:48:46 -0800, Stephen Gildea <stepheng+emacs@gildea.com> said:
Stephen> Version: 27.1
Stephen> commit: 9ce67baa9a3733ae93885b6242130497b13c8703
Stephen> time-stamp: implement numeric time zone conversion
Stephen> * time-stamp.el: Implement %:z as expanding to the numeric time zone
Stephen> offset, to address the feature request of bug#32931. Do not document it
Stephen> yet, to discourage compatibility problems in mixed Emacs 26 and Emacs 27
Stephen> environments. Documentation will be added in a subsequent release at
Stephen> least two years later. (We cannot yet use %z for numeric time zone
Stephen> because in Emacs 26 it was documented to do something else.)
Stephen> * time-stamp-tests.el (time-stamp-test-format-time-zone): expand this
Stephen> test and break it into two tests, time-stamp-test-format-time-zone-name
Stephen> and time-stamp-test-format-time-zone-offset.
If youʼre going to be making changes without documenting them, the
least you can do is follow the commit format conventions.
I donʼt see any reason for not documenting this, you can make it clear
that people mixing emacs 26 and 27 need to be careful.
Robert
next prev parent reply other threads:[~2019-11-07 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 11:04 bug#32931: time-stamp-format: offer numeric time zones too 積丹尼 Dan Jacobson
2019-07-11 16:01 ` Lars Ingebrigtsen
2019-07-11 16:07 ` Lars Ingebrigtsen
2019-07-11 17:01 ` Lars Ingebrigtsen
2019-11-06 16:48 ` Stephen Gildea
2019-11-07 9:02 ` Robert Pluim [this message]
2019-11-07 14:33 ` Eli Zaretskii
2019-11-07 20:57 ` Stephen Gildea
2019-11-07 21:04 ` Eli Zaretskii
2019-11-09 0:09 ` Stephen Gildea
2019-11-09 7:15 ` Eli Zaretskii
2019-11-09 16:51 ` Stephen Gildea
2019-11-09 17:07 ` Eli Zaretskii
2019-11-14 5:16 ` bug#32931: closed: " Stephen Gildea
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lfssvz3l.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=32931@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=stepheng+emacs@gildea.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).