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:00:51 +0300 [thread overview]
Message-ID: <83bn3w675o.fsf@gnu.org> (raw)
In-Reply-To: <f438f691-dd99-9a05-6240-8b52c67017d1@cs.ucla.edu> (message from Paul Eggert on Mon, 23 May 2016 09:44:44 -0700)
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 23 May 2016 09:44:44 -0700
>
> On 05/23/2016 09:32 AM, Eli Zaretskii wrote:
> >> >Closed bugs are not included in the list at the top of
> >> >http://debbugs.gnu.org/19759
> > They are for me.
>
> What I've noticed, is that http://debbugs.gnu.org/19759 is often cached
> (whether in my browser or somewhere else, I haven't checked), and when I
> close a blocking bug the closed bug is still listed on that web page as
> a blocker, until I refresh the cache. This is independent of whether the
> bug is still listed as a blocker.
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.
So if some cache is involved in this, it reacts differently to closing
a bug and to removing it from the blockers list.
> Glenn is right: it shouldn't be necessary to remove the bug as a
> blocking bug. If there is something other than caching that is causing
> this problem it'd be nice to know what it is.
Hey, I tried, okay? I didn't do it because I deliberately ignored
Glenn's requests. I even told him in the past (off list) that what he
asks for didn't work for me. I just don't want to let software
problems prevent me from doing my job. If there's a bug there
somewhere that causes the phenomenon I described above, I'm all for
fixing it, and will be the first to avoid sending control messages
when it is fixed -- it's not like I enjoy writing those messages.
TIA
next prev parent reply other threads:[~2016-05-23 17:00 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 [this message]
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
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=83bn3w675o.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 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.