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 05:44:22 +0300 [thread overview]
Message-ID: <83oa7t35dl.fsf@gnu.org> (raw)
In-Reply-To: <8107393c-81e6-8422-cebf-f372bc0061bd@cs.ucla.edu> (message from Paul Eggert on Wed, 25 May 2016 14:51:32 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 25 May 2016 14:51:32 -0700
>
> > Doing a hard refresh forces Firefox to bypass its cache; but ideally,
> > debbugs should respond correctly to Firefox' queries and indicate that
> > the page was in fact modified.
>
> Yes, the bug is clearly on the debbugs side here. That being said, the
> workaround is to use a shift-reload, which causes Firefox to specify
> "cache-control: no"in its request, which in turn causes debbugs to
> recalculate the page.
The bug seems to be that the removal of a closed bug from the blockers
list takes several hours, which is much more than one can be
reasonably expect to wait. For example, one bug was closed yesterday
6.5 hours before I got to refreshing the list, and then just clicking
the refresh icon showed the updated list. By contrast, explicitly
removing a bug from the list by a debbugs command results in an
instant update that doesn't need any workarounds.
That said, all this thread is a tempest in a teapot, because adding a
bug to the list (if it becomes open again) takes just a few moments.
next prev parent reply other threads:[~2016-05-26 2:44 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 [this message]
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=83oa7t35dl.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 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.