unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: rgm@gnu.org, 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 20:41:51 +0300	[thread overview]
Message-ID: <834m9o659c.fsf@gnu.org> (raw)
In-Reply-To: <d24f454f-b05f-8155-0538-db6a7ae351c5@cs.ucla.edu> (message from Paul Eggert on Mon, 23 May 2016 10:32:08 -0700)

> Cc: rgm@gnu.org, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> 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	other threads:[~2016-05-23 17:41 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 [this message]
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

  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=834m9o659c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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 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).