unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33450@debbugs.gnu.org, mkupfer@alum.berkeley.edu
Subject: bug#33450: 26.1.90; NEWS entry for dired 'Z' is inaccurate
Date: Thu, 22 Nov 2018 13:18:54 -0500	[thread overview]
Message-ID: <i74lc9c6wh.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83muq2gj06.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 22 Nov 2018 00:31:37 +0200")

Eli Zaretskii wrote:

>> And indeed NEWS.25 says "The command 'dired-do-compress', bound to 'Z',
>> now can compress directories", so NEWS.26 is duplicating that.
>
> I see no harm in that, as the NEWS.26 text is more complete and
> accurate (it talks about decompression as well, for starters).

I find this odd.
95% of the 'Z' NEWS.26 entry is true in Emacs 25.1 (by experiment).
The only thing that's different in 26.1 is the .tgz treatment.
This hardly seems NEWS-worthy.

If you for some reason want to keep the expanded entry in NEWS.26, it
should at least be corrected to say "This change was actually made in
Emacs 25.1, but the NEWS entry was too terse" (or however you want to
justfiy re-visiting it). It is incorrect to say "This change was
actually made in Emacs 26.1".

But I think it would be better to move your description from NEWS to the
doc string.





  reply	other threads:[~2018-11-22 18:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21  3:39 bug#33450: 26.1.90; NEWS entry for dired 'Z' is inaccurate Mike Kupfer
2018-11-21  9:23 ` Eli Zaretskii
2018-11-21 14:50   ` Mike Kupfer
2018-11-21 15:13     ` Eli Zaretskii
2018-11-21 15:21       ` Mike Kupfer
2018-11-21 15:39         ` Eli Zaretskii
2018-11-21 18:23 ` Glenn Morris
2018-11-21 20:24   ` Glenn Morris
2018-11-21 22:31     ` Eli Zaretskii
2018-11-22 18:18       ` Glenn Morris [this message]
2018-11-22 19:05         ` Eli Zaretskii
2018-11-22 23:17     ` Richard Stallman
2018-11-23  8:37       ` Eli Zaretskii
2018-11-24  0:10         ` Richard Stallman

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=i74lc9c6wh.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=33450@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mkupfer@alum.berkeley.edu \
    /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).