unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org
Cc: 32252@debbugs.gnu.org, eggert@cs.ucla.edu, eller.helmut@gmail.com
Subject: bug#32252: [PATCH] %o and %x now format signed numbers
Date: Wed, 25 Jul 2018 14:56:04 -0700 (PDT)	[thread overview]
Message-ID: <3f7fb7dd-c008-41d5-8090-5c2213652790@default> (raw)
In-Reply-To: <E1fiAre-0008JK-85@fencepost.gnu.org>

>   > > Although it is indeed an incompatible change, I surveyed the existing
>   > > Emacs source code and couldn't find anything that the change would
>   > > break.
> 
>   > Inadequate.  Never wholly irrelevant, but certainly not
>   > sufficient.  You surveyed something mostly irrelevant.
> 
> How about saying "incomplete"?  It states the valid point but is far less harsh.

Incomplete, of course; thank you.

But also inadequate, IMO - or insufficient, if you prefer - perhaps that is less harsh than inadequate.

The intention was not to be harsh but to say that, while it is good to check the sources distributed with Emacs, it is not good enough.

"Incomplete" tells part of the story, but it doesn't imply that there is a problem. (Unless there is agreement on a completeness requirement -  I wasn't assuming such agreement.)

Saying it's not sufficient to just check the Emacs sources says both that doing so is incomplete _and_ that such an incomplete search is not enough.

But you're no doubt right that there is likely more agreement that such a search is incomplete than there is that it's also not enough.





  reply	other threads:[~2018-07-25 21:56 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 19:12 bug#32252: [PATCH] %o and %x now format signed numbers Paul Eggert
2018-07-23 19:48 ` Helmut Eller
2018-07-23 19:49 ` Drew Adams
2018-07-23 23:30   ` Paul Eggert
2018-07-24  1:20     ` Drew Adams
2018-07-24  2:04       ` Paul Eggert
2018-07-24  2:38         ` Eli Zaretskii
2018-07-24  2:44           ` Paul Eggert
2018-07-24 14:29             ` Eli Zaretskii
2018-07-24  4:15         ` Drew Adams
2018-07-23 23:39 ` Paul Eggert
2018-07-24  1:16   ` Drew Adams
2018-07-25  3:53     ` Richard Stallman
2018-07-25 21:56       ` Drew Adams [this message]
2018-07-27  3:20         ` Richard Stallman
2018-07-24  4:49   ` Helmut Eller
2018-07-24 14:22     ` Paul Eggert
2018-07-24 14:35       ` Andreas Schwab
2018-07-24 18:15       ` Helmut Eller
2018-07-25  0:50         ` Paul Eggert
2018-07-25  2:41           ` Eli Zaretskii
2018-07-25 17:21             ` Paul Eggert
2018-07-25 17:28               ` Eli Zaretskii
2018-07-26  7:44                 ` Paul Eggert
2018-07-26  8:04                   ` Helmut Eller
2018-07-26  8:16                     ` Paul Eggert
2018-07-25  6:58           ` Helmut Eller
2018-07-26  7:59             ` Paul Eggert
2018-07-26  8:43               ` Helmut Eller
2018-07-26  9:15                 ` Paul Eggert
2018-07-26  9:39                   ` Helmut Eller
2018-07-26  9:31                 ` Andreas Schwab
2018-07-26  9:40                   ` Robert Pluim
2018-07-26  9:56                   ` Helmut Eller
2018-07-26 16:55                     ` Paul Eggert
2018-07-26 17:16                       ` Helmut Eller
2018-07-26 17:50                         ` Paul Eggert
2018-07-26 18:35                           ` Helmut Eller
2018-07-26 21:07                             ` Paul Eggert
2018-07-24 18:27     ` Eli Zaretskii
2018-07-25  0:54       ` Paul Eggert
2018-07-25  8:09         ` Andreas Schwab
2018-07-25 20:16           ` Paul Eggert
2018-07-25 14:17         ` Eli Zaretskii
2018-07-25 23:33         ` Brett Gilio
2018-07-26  7:26           ` Paul Eggert
2018-07-24 16:26 ` Andy Moreton
2018-07-25 10:08 ` Andy Moreton
2018-07-26 12:52 ` Andy Moreton
2018-07-26 12:54 ` Andy Moreton
2018-07-26 17:18 ` Helmut Eller
2018-08-23  9:37 ` Helmut Eller
2022-07-04  1:03 ` bug#32252: i find binary-as-unsigned to be very helpful snickerbockers

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=3f7fb7dd-c008-41d5-8090-5c2213652790@default \
    --to=drew.adams@oracle.com \
    --cc=32252@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eller.helmut@gmail.com \
    --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).