[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-sw

From: Eli Zaretskii
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

> Cc: address@hidden, address@hidden
> From: Paul Eggert <address@hidden>
> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]