From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 10057@debbugs.gnu.org
Subject: bug#10057: 24.0.91; doc string of `Info-find-file'
Date: Wed, 16 Nov 2011 20:10:14 +0200 [thread overview]
Message-ID: <83ty64c515.fsf@gnu.org> (raw)
In-Reply-To: <E03D51D3CE5A43EEB0CCA67E83E89AAC@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <monnier@iro.umontreal.ca>, <10057@debbugs.gnu.org>
> Date: Wed, 16 Nov 2011 06:52:29 -0800
>
> > > Apparently, we should not bother to point out when
> > > parameters to functions etc. are undefined/undescribed.
> >
> > No. "We" should of course report such potential omissions,
>
> Not according to Stefan's "general rule": According to that, omission indicates
> clearly to everyone that that the behavior is unpredictable and unsupported.
That's a misrepresentation of what Stefan said. But you already know
that.
> > instead of raising the level of flames and continuing the argument.
>
> It was not I who made a mountain out of this tiny molehill [...]
I rest my case.
next prev parent reply other threads:[~2011-11-16 18:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 20:30 bug#10057: 24.0.91; doc string of `Info-find-file' Drew Adams
2011-11-15 21:39 ` Juri Linkov
2011-11-15 21:56 ` Drew Adams
2011-11-15 22:17 ` Andreas Schwab
2011-11-15 22:21 ` Drew Adams
2011-11-15 21:50 ` Stefan Monnier
2011-11-15 22:08 ` Drew Adams
2011-11-16 2:28 ` Stefan Monnier
2011-11-16 2:29 ` Stefan Monnier
2011-11-16 3:05 ` Drew Adams
2011-11-16 3:24 ` Glenn Morris
2011-11-16 5:23 ` Drew Adams
2011-11-16 4:22 ` Stefan Monnier
2011-11-16 5:24 ` Drew Adams
2011-11-16 8:34 ` Eli Zaretskii
2011-11-16 14:52 ` Drew Adams
2011-11-16 18:10 ` Eli Zaretskii [this message]
2011-11-16 18:29 ` Drew Adams
2011-11-16 18:43 ` Memnon Anon
2011-11-16 19:56 ` Eli Zaretskii
2011-11-16 17:03 ` Juri Linkov
2011-11-16 18:29 ` Drew Adams
2011-11-16 19:31 ` Juri Linkov
2011-11-16 20:04 ` Drew Adams
2011-11-16 20:28 ` Juri Linkov
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=83ty64c515.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10057@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.