From: jlicht@fsfe.org
To: piem@inbox.kyleam.com
Cc: Jelle Licht <jlicht@fsfe.org>
Subject: [PATCH v2 0/5] New piem-debbugs integration.
Date: Fri, 9 Jun 2023 14:48:24 +0200 [thread overview]
Message-ID: <20230609124829.29629-1-jlicht@fsfe.org> (raw)
In-Reply-To: <20230608165926.12586-1-jlicht@fsfe.org>
From: Jelle Licht <jlicht@fsfe.org>
I tidied up the changes, making sure that the :gnu-package
header-matching is only used as a fallback by piem-gnus, and factored
the logic such that the new piem-debbugs integration can also make use
of it..
I copied the copyright blurb, as IANAL, but please adjust according to
your preferences if you don't like it.
Jelle Licht (5):
piem: Add :gnu-package keyword to piem-inboxes
gnus: Skip adding mboxrd from-line when not needed.
piem: Add piem-inbox-by-gnu-package-match.
gnus: Add support for matching inbox by X-GNU-PR-PACKAGE header.
Add basic integration for debbugs.
Documentation/piem.texi | 6 ++++
piem-debbugs.el | 66 +++++++++++++++++++++++++++++++++++++++++
piem-gnus.el | 41 ++++++++++++++++++-------
piem.el | 19 +++++++++++-
4 files changed, 120 insertions(+), 12 deletions(-)
create mode 100644 piem-debbugs.el
--
2.40.1
next prev parent reply other threads:[~2023-06-09 12:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 16:59 [PATCH 1/2] piem: Add :gnu-package keyword to piem-inboxes jlicht
2023-06-08 16:59 ` [PATCH 2/2] gnus: Skip adding mboxrd from-line when not needed jlicht
2023-06-09 12:48 ` jlicht [this message]
2023-06-09 12:48 ` [PATCH v2 1/5] piem: Add :gnu-package keyword to piem-inboxes jlicht
2023-06-10 4:52 ` Kyle Meyer
2023-06-10 10:02 ` Jelle Licht
2023-06-09 12:48 ` [PATCH v2 2/5] gnus: Skip adding mboxrd from-line when not needed jlicht
2023-06-10 4:55 ` Kyle Meyer
2023-06-10 10:07 ` Jelle Licht
2023-06-09 12:48 ` [PATCH v2 3/5] piem: Add piem-inbox-by-gnu-package-match jlicht
2023-06-10 4:57 ` Kyle Meyer
2023-06-10 10:08 ` Jelle Licht
2023-06-09 12:48 ` [PATCH v2 4/5] gnus: Add support for matching inbox by X-GNU-PR-PACKAGE header jlicht
2023-06-10 4:58 ` Kyle Meyer
2023-06-10 10:08 ` Jelle Licht
2023-06-09 12:48 ` [PATCH v2 5/5] Add basic integration for debbugs jlicht
2023-06-10 4:59 ` Kyle Meyer
2023-06-10 10:11 ` Jelle Licht
2023-06-10 5:00 ` [PATCH v2 0/5] New piem-debbugs integration Kyle Meyer
2023-06-10 9:58 ` [PATCH v3 " jlicht
2023-06-10 9:58 ` [PATCH v3 1/5] piem: Add :gnu-package keyword to piem-inboxes jlicht
2023-06-10 9:58 ` [PATCH v3 2/5] gnus: Skip adding mboxrd from-line when not needed jlicht
2023-06-10 9:58 ` [PATCH v3 3/5] piem: Add piem-inbox-by-gnu-package-match jlicht
2023-06-10 23:17 ` Kyle Meyer
2023-06-10 9:58 ` [PATCH v3 4/5] piem-inbox-by-header-match: Fallback to matching via :gnu-package jlicht
2023-06-10 9:58 ` [PATCH v3 5/5] Add basic integration for debbugs jlicht
2023-06-10 23:16 ` [PATCH v3 0/5] New piem-debbugs integration Kyle Meyer
2023-06-10 23:46 ` Jelle Licht
2023-06-11 0:55 ` Kyle Meyer
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://git.kyleam.com/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230609124829.29629-1-jlicht@fsfe.org \
--to=jlicht@fsfe.org \
--cc=piem@inbox.kyleam.com \
/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.kyleam.com/piem/
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).