From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-switch
Date: Mon, 23 May 2016 19:32:25 +0300 [thread overview]
Message-ID: <83k2ik68h2.fsf@gnu.org> (raw)
In-Reply-To: <sm1t4slr3z.fsf@fencepost.gnu.org> (message from Glenn Morris on Mon, 23 May 2016 11:40:48 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: Emacs developers <emacs-devel@gnu.org>
> Date: Mon, 23 May 2016 11:40:48 -0400
>
> GNU bug tracker automated control server wrote:
>
> > Processing commands for control@debbugs.gnu.org:
> >
> >> unblock 19759 by 23050
>
> Again, this is not necessary.
I remembered you said that, but the facts are otherwise, sorry.
> Closed bugs are not included in the list at the top of
> http://debbugs.gnu.org/19759
They are for me. I do need glasses, but I still see very well, I
assure you.
> Explicitly unblocking closed bugs is harmful, because if the bug needs
> to be reopened for some reason, it won't reappear in the blocking list.
Sorry, I have no other way to display the list of blockers as it
really is. Maybe it's a debbugs bug, I don't know. But the problem
is real, and I did the only thing I know about that helps.
next prev parent reply other threads:[~2016-05-23 16:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83oa7x5wpc.fsf@gnu.org>
[not found] ` <handler.s.C.146397087814700.transcript@debbugs.gnu.org>
2016-05-23 15:40 ` Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-switch Glenn Morris
2016-05-23 16:32 ` Eli Zaretskii [this message]
2016-05-23 16:44 ` Paul Eggert
2016-05-23 17:00 ` Eli Zaretskii
2016-05-23 17:32 ` Paul Eggert
2016-05-23 17:41 ` Eli Zaretskii
2016-05-23 18:28 ` John Wiegley
2016-05-23 18:39 ` John Mastro
2016-05-23 18:48 ` Eli Zaretskii
2016-05-24 3:50 ` John Wiegley
2016-05-24 15:38 ` Glenn Morris
2016-05-24 15:41 ` Kaushal Modi
2016-05-24 15:59 ` Eli Zaretskii
2016-05-24 16:47 ` Paul Eggert
2016-05-24 17:25 ` Eli Zaretskii
2016-05-25 1:22 ` Chad Brown
2016-05-25 2:46 ` Eli Zaretskii
2016-05-25 5:13 ` Paul Eggert
2016-05-26 17:00 ` Glenn Morris
2016-05-26 18:09 ` Glenn Morris
2016-05-25 18:23 ` Paul Eggert
2016-05-25 18:51 ` Clément Pit--Claudel
2016-05-25 18:56 ` Clément Pit--Claudel
2016-05-25 19:33 ` Dmitry Gutov
2016-05-25 21:51 ` Paul Eggert
2016-05-26 2:44 ` Eli Zaretskii
2016-05-26 5:08 ` Paul Eggert
2016-05-26 15:09 ` Eli Zaretskii
2016-05-26 15:27 ` Paul Eggert
2016-05-26 15:48 ` Eli Zaretskii
2016-05-26 16:01 ` Paul Eggert
2016-05-26 16:43 ` John Wiegley
2016-05-26 16:51 ` Paul Eggert
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=83k2ik68h2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.