From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: John Wiegley <jwiegley@gmail.com>,
bozhidar@batsov.com, emacs-devel@gnu.org
Subject: Re: Very happy with emacs-25 so far
Date: Sun, 20 Mar 2016 11:34:19 +0100 [thread overview]
Message-ID: <m3io0hjv4k.fsf@gnus.org> (raw)
In-Reply-To: <83k2kx7reo.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Mar 2016 05:35:27 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> What is the purpose of marking them as blocking the release if we
> don't really mean that?
I think there can be disagreement about how blocking these blocking bugs
are. From the current list:
New Emacs icon blurry in GNOME on Fedora
Support linking -ldl on Hurd
xwidget-webkit-scroll-behaviour = image is non-functional
etc.
Just reading over the list, they all seem like bugs that should be
fixed, but I'd say two thirds of them are bugs that we could live with
in Emacs 25.1. Or four fifths. And at the rate they're being fixed,
I'd guess the actual ratio is nine tenths. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-03-20 10:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 23:28 Very happy with emacs-25 so far John Wiegley
2016-03-19 17:45 ` Bozhidar Batsov
2016-03-19 18:53 ` Eli Zaretskii
2016-03-19 23:09 ` John Wiegley
2016-03-20 3:35 ` Eli Zaretskii
2016-03-20 10:34 ` Lars Magne Ingebrigtsen [this message]
2016-03-20 16:23 ` Eli Zaretskii
2016-03-20 16:38 ` Bozhidar Batsov
2016-03-21 17:52 ` John Wiegley
2016-03-21 18:37 ` Eli Zaretskii
2016-03-21 21:15 ` John Wiegley
2016-03-21 22:22 ` Nicolas Petton
2016-03-21 22:38 ` Michael Heerdegen
2016-03-21 23:04 ` Paul Eggert
2016-03-22 3:31 ` Eli Zaretskii
2016-03-21 20:13 ` Paul Eggert
2016-03-22 0:14 ` Rostislav Svoboda
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=m3io0hjv4k.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=bozhidar@batsov.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.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.