From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: larsi@gnus.org, schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus
Date: Tue, 31 Mar 2020 20:59:01 +0300 [thread overview]
Message-ID: <83y2rgz9qy.fsf@gnu.org> (raw)
In-Reply-To: <m2d08s1p0p.fsf@gmail.com> (message from Robert Pluim on Tue, 31 Mar 2020 18:13:10 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
> emacs-devel@gnu.org
> Date: Tue, 31 Mar 2020 18:13:10 +0200
>
> Now that Iʼve actually tested it, the change looks like this, making
> make-network-process and make-serial process behave the same as
> make-process and make-pipe-process. Iʼve looked at all uses of those
> two functions in Emacs' sources, and none of them depend on the change
> in semantics, in fact only a couple of them actually pass a :coding
> keyword.
Nevertheless, we should call out this change in NEWS.
> Having said all that, this does go back a looooong way (2002 at
> least), so maybe we want to let sleeping dogs lie.
I don't think this is a risky change. Programs that assume what we
currently do rely on undefined behavior, IMO.
Thanks.
next prev parent reply other threads:[~2020-03-31 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86bloi1zrj.fsf@csic.es>
[not found] ` <83lfnm8b30.fsf@gnu.org>
[not found] ` <83ftdt9b1d.fsf@gnu.org>
[not found] ` <86sght3h1s.fsf@csic.es>
[not found] ` <834ku89anf.fsf@gnu.org>
[not found] ` <87a740ub2r.fsf@gnus.org>
[not found] ` <83tv287s9j.fsf@gnu.org>
[not found] ` <874ku7txho.fsf@gnus.org>
[not found] ` <83imin5l0w.fsf@gnu.org>
2020-03-31 9:20 ` bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus Robert Pluim
2020-03-31 9:53 ` Andreas Schwab
2020-03-31 10:16 ` Robert Pluim
2020-03-31 10:31 ` Andreas Schwab
2020-03-31 11:09 ` Robert Pluim
2020-03-31 16:13 ` Robert Pluim
2020-03-31 17:59 ` Eli Zaretskii [this message]
2020-03-31 19:53 ` Robert Pluim
2020-04-02 11:10 ` Lars Ingebrigtsen
2020-04-02 12:48 ` Robert Pluim
2020-04-03 11:52 ` Lars Ingebrigtsen
2020-04-03 12:50 ` Robert Pluim
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=83y2rgz9qy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.com \
--cc=schwab@linux-m68k.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).