From: Ted Zlatanov <tzz@lifelogs.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 17217@debbugs.gnu.org, "Lars Ingebrigtsen" <larsi@gnus.org>,
"João Távora" <joaotavora@gmail.com>
Subject: bug#17217: 24.4.50; eww/shr and relative links
Date: Tue, 04 Nov 2014 15:14:47 -0500 [thread overview]
Message-ID: <87d29267uw.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <islhnqeomc.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 04 Nov 2014 14:45:31 -0500, Tue, 04 Nov 2014 14:55:43 -0500")
On Tue, 04 Nov 2014 14:45:31 -0500 Glenn Morris <rgm@gnu.org> wrote:
GM> I don't know why you guys are confused. You know the bug is closed, because
GM> i) you (João) closed it
GM> ii) you (Ted) had to unarchive it to have this conversation, and only
GM> closed bugs get archived.
I thought archiving applied to inactive bugs, not just closed ones. So I
unarchived thinking "it's been inactive."
Thanks for explaining.
GM> And the change is (of course) already in trunk thanks to the "automatic"
GM> merging that has gone on as long as the emacs-24 branch has existed.
GM> There's nothing to do here.
That's what I thought, but I didn't see the change. It was pilot error:
I used bzr log incorrectly and missed the merge commit.
GM> PS Ted, whatever method you are using to find bugs, it should exclude
GM> closed ones (certainly archived ones). Both the debbugs.gnu.org search
GM> and (I believe) debbugs.el do so by default.
OK, thanks, will do. Sorry for the noise.
Ted
next prev parent reply other threads:[~2014-11-04 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 13:03 bug#17217: 24.4.50; eww/shr and relative links João Távora
2014-04-07 21:01 ` João Távora
2014-04-11 15:08 ` João Távora
[not found] ` <871tpi7w16.fsf@lifelogs.com>
2014-11-04 18:42 ` João Távora
2014-11-04 18:51 ` Ted Zlatanov
2014-11-04 19:36 ` João Távora
2014-11-04 19:45 ` Glenn Morris
2014-11-04 19:55 ` Glenn Morris
2014-11-04 20:14 ` Ted Zlatanov [this message]
2014-11-04 21:10 ` João Távora
2014-11-05 16:52 ` Glenn Morris
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=87d29267uw.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=17217@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=larsi@gnus.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).