From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, hendrik.tews@kernkonzept.com, 45438@debbugs.gnu.org
Subject: bug#45438: 27.1; please fix misleading documentation for assoc-delete-all
Date: Sun, 27 Dec 2020 19:47:06 +0200 [thread overview]
Message-ID: <83k0t3kup1.fsf@gnu.org> (raw)
In-Reply-To: <E1ktOlC-0007BQ-HE@fencepost.gnu.org> (message from Richard Stallman on Sun, 27 Dec 2020 00:38:30 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: larsi@gnus.org, hendrik.tews@kernkonzept.com,
> 45438@debbugs.gnu.org
> Date: Sun, 27 Dec 2020 00:38:30 -0500
>
> > If the suggestion is to use ChangeLog data for this feature, then I
> > think it won't be easy, because it isn't easy to parse the ChangeLog
> > text for gleaning this more accurate information.
>
> I'm not suggesting we do anything about this problem. Do you see
> any reason to?
We were asked to consider doing that by 2 different people. I agree
that the problem is not an urgent one nor a grave one, but if someone
wants to work on making that part of documentation more accurate, I
think gleaning the info from ChangeLog is not the best approach.
next prev parent reply other threads:[~2020-12-27 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 22:13 bug#45438: 27.1; please fix misleading documentation for assoc-delete-all Hendrik Tews
2020-12-25 22:32 ` Lars Ingebrigtsen
2020-12-26 10:28 ` Richard Stallman
2020-12-26 10:58 ` Eli Zaretskii
2020-12-26 21:56 ` Lars Ingebrigtsen
2020-12-27 5:38 ` Richard Stallman
2020-12-27 17:47 ` Eli Zaretskii [this message]
2020-12-28 5:25 ` Richard Stallman
2020-12-26 21:04 ` Hendrik Tews
2020-12-26 21:17 ` Hendrik Tews
[not found] <<87zh21fsb3.fsf@cert.kernkonzept.com>
[not found] ` <<87blehcyai.fsf@gnus.org>
[not found] ` <<E1kt6no-0002VV-Ma@fencepost.gnu.org>
[not found] ` <<834kk8n8a8.fsf@gnu.org>
2020-12-26 18:59 ` Drew Adams
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=83k0t3kup1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45438@debbugs.gnu.org \
--cc=hendrik.tews@kernkonzept.com \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
/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).