Bug#962216: marked as done (journalctl -f --boot header perhaps not appropriate)

[Debian Bug Tracking System]

Your message dated Sun, 07 Jun 2020 01:36:29 +0800
with message-id <87bllwgkpu.5.fsf at jidanni.org>
and subject line Re: Bug#962216: journalctl -f --boot header perhaps not appropriate
has caused the Debian Bug report #962216,
regarding journalctl -f --boot header perhaps not appropriate
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
962216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962216
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: =?utf-8?B?56mN5Li55bC8?= Dan Jacobson <jidanni at jidanni.org>
Subject: journalctl -f --boot header perhaps not appropriate
Date: Fri, 05 Jun 2020 00:48:23 +0800
Size: 4646
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200606/19f1428d/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: =?utf-8?B?56mN5Li55bC8?= Dan Jacobson <jidanni at jidanni.org>
Subject: Re: Bug#962216: journalctl -f --boot header perhaps not appropriate
Date: Sun, 07 Jun 2020 01:36:29 +0800
Size: 6130
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200606/19f1428d/attachment-0001.mht>