From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: ahyatt@gmail.com, arturmalabarba@gmail.com, emacs-devel@gnu.org,
dgutov@yandex.ru, acm@muc.de, larsi@gnus.org
Subject: Re: [Emacs-diffs] emacs-25 d0d9f55: Allow newlines inside cl function arglists
Date: Thu, 12 May 2016 22:23:52 +0300 [thread overview]
Message-ID: <83inyj9j1z.fsf@gnu.org> (raw)
In-Reply-To: <m2a8jxcqn7.fsf@newartisans.com> (message from John Wiegley on Tue, 10 May 2016 18:47:08 -0700)
> From: John Wiegley <jwiegley@gmail.com>
> Date: Tue, 10 May 2016 18:47:08 -0700
> Cc: Andrew Hyatt <ahyatt@gmail.com>, Artur Malabarba <arturmalabarba@gmail.com>,
> Dmitry Gutov <dgutov@yandex.ru>, Alan Mackenzie <acm@muc.de>,
> Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
>
> I'm wondering if you and some of other core devs would be willing to spend a
> few days scanning through the blocking bugs list[1], to see which ones really
> need to be fixed in the next month, and which can be deferred until later?
We'd need clear criteria for nominating blocking bug reports. Could
you publish what you think should be those criteria?
next prev parent reply other threads:[~2016-05-12 19:23 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 [this message]
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
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
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=83inyj9j1z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=ahyatt@gmail.com \
--cc=arturmalabarba@gmail.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=larsi@gnus.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).