From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: clement.pit@gmail.com, emacs-devel@gnu.org
Subject: Re: Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-switch
Date: Thu, 26 May 2016 18:09:53 +0300 [thread overview]
Message-ID: <83lh2w3lfi.fsf@gnu.org> (raw)
In-Reply-To: <574684CE.9020900@cs.ucla.edu> (message from Paul Eggert on Wed, 25 May 2016 22:08:30 -0700)
> Cc: clement.pit@gmail.com, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 25 May 2016 22:08:30 -0700
>
> Eli Zaretskii wrote:
> > The bug seems to be that the removal of a closed bug from the blockers
> > list takes several hours
>
> That's not been my experience. There is never a several-hour wait. If I close
> the blocking bug B via email, and wait a minute or two and verify that it's
> closed by visiting its bug page and forcing a refresh, and then visit
> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19759>, what I observe is that
> Bug#19759 still lists B as blocking (due to the debbugs bug). If I refresh the
> Bug#19759 page in the routine way it will continue to list B as blocking. If I
> do a full refresh (by shift-left-mouse-click) then the Bug#19759 page will no
> longer list B as blocking; this is always immediate, assuming B has been closed
> already.
I was talking about a simple refresh, not forced refresh.
And it looks like a problem is more complex than I thought: on one
machine I tried this even 24 hours was not enough to refresh the page.
> > adding a
> > bug to the list (if it becomes open again) takes just a few moments.
>
> Sure, but it's easy to forget to add B as a blocker, and indeed the person
> reopening B may not even know that B was a blocker and should become a blocker
> again. In contrast, simply closing B in the first place will mean that reopening
> B later will do the right thing without further thought.
You can rely on me: I won't forget.
next prev parent reply other threads:[~2016-05-26 15:09 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
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 [this message]
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
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=83lh2w3lfi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=clement.pit@gmail.com \
--cc=eggert@cs.ucla.edu \
--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 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).