From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 32931@debbugs.gnu.org, stepheng+emacs@gildea.com, jidanni@jidanni.org
Subject: bug#32931: time-stamp-format: offer numeric time zones too
Date: Thu, 07 Nov 2019 16:33:58 +0200 [thread overview]
Message-ID: <837e4bg3hl.fsf@gnu.org> (raw)
In-Reply-To: <m2lfssvz3l.fsf@gmail.com> (message from Robert Pluim on Thu, 07 Nov 2019 10:02:06 +0100)
> Date: Thu, 07 Nov 2019 10:02:06 +0100
> Cc: 32931@debbugs.gnu.org,
> 積丹尼 Dan Jacobson <jidanni@jidanni.org>
>
> 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.
Indeed, please be sure to mention such changes in NEWS. Bonus points
for updating the relevant manual(s) as well.
We had in the past important changes that were left undocumented
because we forgot to update NEWS and the manuals when the code was
added. So I'd like to urge everybody to please go extra mile and push
documentation changes together with code changes.
TIA
next prev parent reply other threads:[~2019-11-07 14:33 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
2019-11-07 14:33 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837e4bg3hl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32931@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=rpluim@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.