From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: Summary buffer, limit to the registry marks
Date: Wed, 05 Jan 2022 14:51:47 +0100 [thread overview]
Message-ID: <87o84qb898.fsf@mat.ucm.es> (raw)
In-Reply-To: <87mtkrym6c.fsf@ericabrahamsen.net>
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
> Nope, you're right, limit to marks doesn't check registry marks. Hang on
> and I'll open a bug report for this.
I cannot find your bug report, when did you submit it?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-01-05 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 16:07 Uwe Brauer
2021-12-22 18:54 ` Emanuel Berg
2021-12-23 16:38 ` Uwe Brauer
2021-12-23 18:30 ` Eric Abrahamsen
2021-12-23 21:21 ` Uwe Brauer
2021-12-23 22:46 ` Eric Abrahamsen
2021-12-23 22:48 ` Emanuel Berg
2022-01-05 13:51 ` Uwe Brauer [this message]
2022-01-06 18:34 ` Eric Abrahamsen
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=87o84qb898.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).