From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: michael_heerdegen@web.de, adam@alphapapa.net, acorallo@gnu.org,
71370@debbugs.gnu.org
Subject: bug#71370: 30.0.50; Please un-obsolete buffer-substring as a generalized variable
Date: Sat, 22 Jun 2024 12:45:03 +0300 [thread overview]
Message-ID: <86a5jdia5c.fsf@gnu.org> (raw)
In-Reply-To: <87cyo9id71.fsf@localhost> (message from Ihor Radchenko on Sat, 22 Jun 2024 08:39:14 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: michael_heerdegen@web.de, adam@alphapapa.net, 71370@debbugs.gnu.org,
> acorallo@gnu.org
> Date: Sat, 22 Jun 2024 08:39:14 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Do note that the original reason of obsoletion was different:
> > ...
> > Commit log messages are not a legal document, so treating them as if
> > they were the truth, the whole truth, and nothing but the truth is not
> > TRT.
>
> I am not saying that commit message is the full truth.
> But I did not find any other relevant discussion about
> `buffer-substring' on the mailing list. (And commit message did not
> contain any reference to such discussion)
>
> So, I simply used information that was available to me to check
> Michaels' claim.
>
> If you have a link to the discussion leading to obsolete of
> `buffer-substring', feel free to share it.
I respectfully suggest to consider this discussion as relevant
evidence.
next prev parent reply other threads:[~2024-06-22 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 1:33 bug#71370: 30.0.50; Please un-obsolete buffer-substring as a generalized variable Adam Porter
2024-06-05 11:52 ` Eli Zaretskii
2024-06-05 12:09 ` Ihor Radchenko
2024-06-05 14:16 ` Adam Porter
2024-06-05 14:58 ` Eli Zaretskii
2024-06-05 17:35 ` Adam Porter
2024-06-19 23:44 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 4:05 ` Adam Porter
2024-06-20 15:33 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 15:46 ` Ihor Radchenko
2024-06-21 8:55 ` Andrea Corallo
2024-06-21 22:52 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 6:05 ` Ihor Radchenko
2024-06-22 8:16 ` Eli Zaretskii
2024-06-22 8:39 ` Ihor Radchenko
2024-06-22 9:45 ` Eli Zaretskii [this message]
2024-06-22 7:13 ` Eli Zaretskii
2024-06-27 15:09 ` Adam Porter
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=86a5jdia5c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71370@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=adam@alphapapa.net \
--cc=michael_heerdegen@web.de \
--cc=yantar92@posteo.net \
/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).