From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Removing bugs from the blockers
Date: Fri, 13 May 2016 11:36:49 +0300 [thread overview]
Message-ID: <831t569wwu.fsf@gnu.org> (raw)
In-Reply-To: <c8afe70b-d6bf-addd-0009-95e4ab503411@yandex.ru> (message from Dmitry Gutov on Fri, 13 May 2016 00:35:37 +0300)
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 13 May 2016 00:35:37 +0300
>
> 20420 is not very important, and likely wontfix.
> 22107 - same.
> 22527 is not very important.
> 19479 is a crapfest, and is unlikely to be fixed soon (we haven't even
> fixed the basic signature verification functionality yet, see the other
> bugs, and that's shameful).
Agreed. Additional triage:
22434 -- caused by fixing another bug, affects a minor feature, and
won't be fixed unless someone motivated works on it
23144 -- we don't know how to fix it; maybe talking to GTK maintainers
could help
22884 -- IMO we did everything possible, so the bug could be closed
22338 -- shows up only in rare situations, and reasons are not well
understood; suggest to close
17976 -- actually, a feature request, so should not be blocking
20352 -- I thought this was recently resolved, no?
21489 -- is most probably the result of refactoring of keystroke
echoing, and probably won't be fixed
17693 -- not reproducible on my machine, and no one responded to my
request for reproduction
23360 -- does anyone have a better idea than introducing a variable to
control the affected code (which is mostly unneeded, but
sometimes is)?
22440 -- someone who knows about package.el should look at this
21650 -- MH-E bug, handled there
23513 -- includes a patch; someone who knows about package.el should
look at this
22795 -- not reproducible, should probably be closed, as I've not
heard from the OP for a long time
22465 -- includes a patch that should be applied, and the bug closed
20247 -- appears in very rare situations, so shouldn't block the
release
21182 -- the blamed commit seems unrelated, so should probably be
tagged not reproducible
19548 -- is worded too generally, and is therefore hard to work on;
perhaps Glenn could make post specific complaints, which then
could be handled one by one
23050 -- is a manifestation of an old bug 18125, and also includes 2
ideas for solution; also, is specific to a certain workflow,
so there's a workaround
21871 -- discussion ends with an unanswered question to Stefan
22527 -- sounds like it should be closed?
21422 -- my opinion on that is in the discussion; 'nuff said
19717 -- a patch was suggested not long ago; can someone review it?
21874 -- sounds like it should be closed?
22295 -- undo-related, I hope Phillip will be able to look into it
22147 -- should be closed, I think (why is it on the blocking list?)
My conclusion from reviewing these bugs is: I don't really understand
how come some of the bugs were designated as "blocking".
A more general conclusion (from both these and other bug reports) is
that we tend to break valid use cases when we refactor some core parts
of Emacs, and the people who worked on refactoring are not always
willing to work on cleaning up the breakage it caused. For example,
the above list includes a few bugs for which the offending commit was
identified, but the guilty parties don't seem to be eager to work on
that.
next prev parent reply other threads:[~2016-05-13 8:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160509235343.17047.73943@vcs.savannah.gnu.org>
[not found] ` <20160509235343.759D0220128@vcs.savannah.gnu.org>
2016-05-10 1:34 ` [Emacs-diffs] emacs-25 d0d9f55: Allow newlines inside cl function arglists Stefan Monnier
2016-05-10 10:11 ` Dmitry Gutov
2016-05-10 10:21 ` Andreas Schwab
2016-05-10 10:31 ` Dmitry Gutov
2016-05-10 11:27 ` Andreas Schwab
2016-05-10 11:33 ` Dmitry Gutov
2016-05-10 11:57 ` Andreas Schwab
2016-05-10 12:01 ` Dmitry Gutov
2016-05-10 12:36 ` Andreas Schwab
2016-05-10 12:49 ` Dmitry Gutov
2016-05-10 21:14 ` Stefan Monnier
2016-05-10 21:26 ` Dmitry Gutov
2016-05-11 0:39 ` Dmitry Gutov
2016-05-11 22:40 ` Dmitry Gutov
2016-05-11 1:47 ` John Wiegley
2016-05-12 19:23 ` Eli Zaretskii
2016-05-12 21:23 ` John Wiegley
2016-05-13 8:47 ` Eli Zaretskii
2016-05-13 16:26 ` John Wiegley
2016-05-12 21:35 ` Removing bugs from the blockers Dmitry Gutov
2016-05-13 8:36 ` Eli Zaretskii [this message]
2016-05-13 10:30 ` Lars Ingebrigtsen
2016-05-13 14:12 ` Eli Zaretskii
2016-05-13 16:28 ` John Wiegley
2016-05-13 20:20 ` Lars Ingebrigtsen
2016-05-16 17:51 ` Eli Zaretskii
2016-05-13 12:48 ` Dmitry Gutov
2016-05-13 16:33 ` John Wiegley
2016-06-09 13:04 ` Nix
2016-06-09 21:09 ` bug#21182 (was Removing bugs from the blockers) Mike Kupfer
2016-06-10 11:33 ` Nix
2016-05-13 11:30 ` Removing bugs from the blockers Kaushal Modi
2016-05-13 11:38 ` Dmitry Gutov
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=831t569wwu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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 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.