Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header

To: Ben Finney <bignose@debian.org>, 836613@bugs.debian.org
Subject: Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header
From: Don Armstrong <don@debian.org>
Date: Sun, 4 Sep 2016 16:44:14 -0700
Message-id: <[🔎] 20160904234414.b6ipl22ezlyl6pvi@qor.donarmstrong.com>
Reply-to: Don Armstrong <don@debian.org>, 836613@bugs.debian.org
In-reply-to: <[🔎] 20160904130815.xjm4qtzq5ckflzdz@benfinney.id.au>
References: <[🔎] 20160904130815.xjm4qtzq5ckflzdz@benfinney.id.au>

On Sun, 04 Sep 2016, Ben Finney wrote:
> The ‘debbugs’ server has evidently retrieved a completely different
> text, some “Received” field from the message header. This fails to
> meet the behaviour described in the documentation.

Hrm; yeah, that was working in the past, and what you saw now is
definitely a bug. Thanks for reporting it!


-- 
Don Armstrong                      https://www.donarmstrong.com

I'm So Meta, Even This Acronym
-- xkcd http://xkcd.com/917/

Reply to:

Follow-Ups:
- Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header
  - From: Ben Finney <bignose@debian.org>

References:
- Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header
  - From: Ben Finney <bignose@debian.org>

Prev by Date: Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header
Next by Date: Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header
Previous by thread: Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header
Next by thread: Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header
Index(es):
- Date
- Thread