From: Daniel Mendler <mail@daniel-mendler.de>
To: 48404@debbugs.gnu.org
Subject: bug#48404:
Date: Fri, 14 May 2021 09:50:45 +0200 [thread overview]
Message-ID: <52744ef2-304f-b037-2fae-2f97d6732b38@daniel-mendler.de> (raw)
In-Reply-To: <875yzms6im.fsf@gnu.org>
If the check does not work reliably for third-party packages, it should
probably better reverted altogether. Why slap an ignore-errors around
the broken code now?
According to the commit message, which introduced this bug, there has
been some alternative solution, which clearly sounds better: Either omit
obsolete commands altogether or annotate them as obsolete. Omitting is
probably too problematic since people may rely on running obsolete commands.
What about making the behavior around obsolete commands a customizable
option? 1. omit obsolete commands, 2. annotate obsolete commands, 3. do
nothing.
next prev parent reply other threads:[~2021-05-14 7:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 20:45 bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command Tassilo Horn
2021-05-14 6:21 ` Eli Zaretskii
2021-05-14 6:47 ` Tassilo Horn
2021-05-14 7:18 ` Eli Zaretskii
2021-05-14 7:28 ` Eli Zaretskii
2021-05-14 7:43 ` Lars Ingebrigtsen
2021-05-14 7:56 ` Eli Zaretskii
2021-05-16 14:06 ` Lars Ingebrigtsen
2021-05-16 14:27 ` Eli Zaretskii
2021-05-16 14:38 ` Lars Ingebrigtsen
2021-05-16 14:48 ` Eli Zaretskii
2021-05-17 13:54 ` Lars Ingebrigtsen
2021-05-17 14:10 ` Eli Zaretskii
2021-05-17 14:20 ` Lars Ingebrigtsen
2021-05-17 14:27 ` Eli Zaretskii
2021-05-18 13:31 ` Lars Ingebrigtsen
2021-05-19 11:54 ` Tassilo Horn
2021-05-19 13:59 ` Eli Zaretskii
2021-05-14 7:41 ` Lars Ingebrigtsen
2021-05-14 16:45 ` Stefan Kangas
2021-05-14 16:51 ` Lars Ingebrigtsen
2021-05-14 7:50 ` Daniel Mendler [this message]
2021-05-14 18:31 ` bug#48404: Daniel Mendler
2021-05-16 14:09 ` bug#48404: Lars Ingebrigtsen
2021-05-16 20:26 ` bug#48404: Daniel Mendler
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=52744ef2-304f-b037-2fae-2f97d6732b38@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=48404@debbugs.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 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.