From: Boruch Baum <boruch_baum@gmx.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 34338@debbugs.gnu.org
Subject: bug#34338: 26.1; delete-file return codes and failures
Date: Wed, 30 Oct 2019 18:22:00 -0400 [thread overview]
Message-ID: <20191030222159.rwfn7clgfjh36dze@E15-2016.optimum.net> (raw)
In-Reply-To: <87wocmvt5w.fsf@joffe.skangas.se>
How is it backwards incompatable? If the prior behavior was undefined,
no one would have been using it for anything. From their perspective, a
defined is just another form of undefined behavior, if you get my drift.
On 2019-10-30 22:07, Stefan Kangas wrote:
> tags 34338 + wontfix
> close 34338
> quit
>
> Stefan Kangas <stefan@marxist.se> writes:
>
> > It seems to me from the discussion like we don't want to make the
> > proposed change, since it has an unclear benefit and is backwards
> > incompatible.
> >
> > Is there is something I'm missing here? Otherwise, I think we can
> > close this as wontfix.
>
> No one has objected within 3 weeks, so I'm closing this as wontfix.
>
> Best regards,
> Stefan Kangas
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2019-10-30 22:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 21:47 bug#34338: 26.1; delete-file return codes and failures Boruch Baum
2019-02-06 8:24 ` Michael Albinus
2019-02-06 9:35 ` Boruch Baum
2019-02-06 16:19 ` Eli Zaretskii
2019-02-06 21:02 ` Boruch Baum
2019-02-07 3:36 ` Eli Zaretskii
2019-02-07 5:14 ` Boruch Baum
2019-10-09 11:48 ` Stefan Kangas
2019-10-30 21:07 ` Stefan Kangas
2019-10-30 22:22 ` Boruch Baum [this message]
2019-10-30 22:52 ` Stefan Kangas
2019-10-31 1:33 ` Boruch Baum
2019-10-31 14:32 ` Eli Zaretskii
2019-11-01 9:34 ` Boruch Baum
2019-11-01 9:55 ` Eli Zaretskii
2019-11-08 13:00 ` Stefan Kangas
2019-10-31 14:01 ` Eli Zaretskii
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=20191030222159.rwfn7clgfjh36dze@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=34338@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).