unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Gildea <stepheng+emacs@gildea.com>
Cc: rpluim@gmail.com, 32931@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#32931: time-stamp-format: offer numeric time zones too
Date: Thu, 07 Nov 2019 23:04:56 +0200	[thread overview]
Message-ID: <83d0e3e6tj.fsf@gnu.org> (raw)
In-Reply-To: <9939.1573160269@tigger3.sg.gildea.net> (message from Stephen Gildea on Thu, 07 Nov 2019 12:57:49 -0800)

> From: Stephen Gildea <stepheng+emacs@gildea.com>
> cc: 32931@debbugs.gnu.org, jidanni@jidanni.org,
>     Robert Pluim <rpluim@gmail.com>
> Date: Thu, 07 Nov 2019 12:57:49 -0800
> 
> In September I updated the documentation for changes implemented
> previously; that commit included a section in NEWS.  I will eventually
> document the change that sparked this discussion, too, and I'll add it
> to NEWS at the same time.
> 
> So while I am aware of my responsibility to document, I am also
> mindful of my responsibility to not document yet.

Thanks, but IME deferring the update of documentation for these
reasons is a mistake.  It frequently causes us to forget to make those
deferred updates, and more importantly, it leaves those who use the
development snapshots with outdated or lacking documentation.

I understand the wish to avoid unnecessary rework, but I don't think
there's a way around that.





  reply	other threads:[~2019-11-07 21:04 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
2019-11-07 20:57       ` Stephen Gildea
2019-11-07 21:04         ` Eli Zaretskii [this message]
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=83d0e3e6tj.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 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).