[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: Mon, 23 May 2016 20:41:51 +0300

> Cc: address@hidden, address@hidden
> From: Paul Eggert <address@hidden>
> Date: Mon, 23 May 2016 10:32:08 -0700
> On 05/23/2016 10:00 AM, Eli Zaretskii wrote:
> > IME, the bug is still listed as blocking long after it was closed, no
> > matter how many times I refresh the browser page.  But when I send the
> > control message to the tracker that unblocks it, the next refresh of
> > the browser updates the display by removing that bug.
> Weird, that's not my experience: if I close a blocking bug, wait for a 
> bit (to make sure my bug-close email has hit the debbugs server), and 
> hard-refresh <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19759>, the 
> blocking bug is no longer listed as a blocker.
> I hard-refresh by using Firefox. I hold down the shift key, and press on 
> the cycle icon at the right of the main URL.

My point is that no such hard-refresh (about whose existence I didn't
even know) is needed when I send the control command to the tracker to
remove a big from the blocking list.

> Perhaps the next time you close a blocking bug B, you might try looking 
> at B's page first and waiting until it's marked "done", and then try 
> refreshing Bug#19759.

That's what I did.  The bug was "done", but refereshing the 19759 page
didn't remove it.  When I sent the control message, it was removed on
the next refresh a few minutes later.

reply via email to

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