discussion and development of piem
 help / color / mirror / code / Atom feed
From: Jelle Licht <jlicht@fsfe.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: piem@inbox.kyleam.com
Subject: Re: [PATCH v3 0/5] New piem-debbugs integration
Date: Sun, 11 Jun 2023 01:46:14 +0200	[thread overview]
Message-ID: <87zg56anjt.fsf@fsfe.org> (raw)
In-Reply-To: <874jne29hx.fsf@kyleam.com>

Kyle Meyer <kyle@kyleam.com> writes:

> jlicht@fsfe.org writes:
>
>> From: Jelle Licht <jlicht@fsfe.org>
>>
>> V3 of this series addresses most of the shortcomings identified in the
>> review of V2, with a point-by-point response still on its way.
>
> Thanks, v2 vs v3 range-diff included below.  Pushed (0a8def10) with one
> minor that I'll mention in a direct reply.

Thanks for the timely reviews and help!

I am already making use of the latest-and-greatest using the following
guix package expression, and everything I care about seems to work well.

--8<---------------cut here---------------start------------->8---
(define-public emacs-piem-next
  (let ((commit "0a8def1045ac083fb8c9d523cefed91155bfb593")
        (revision "0"))
    (package
      (inherit emacs-piem)
      (version (git-version (package-version emacs-piem) revision commit))
      (source (origin
              (method git-fetch)
              (uri (git-reference
                    (url "https://git.kyleam.com/piem")
                    (commit commit)))
              (file-name (git-file-name (package-name emacs-piem) version))
              (sha256
               (base32
                "1mwncvhrgqkh09bg7mzb2z66p2dnxd8bchcszs9y49cgvqllw9hp"))))
      (propagated-inputs
       (modify-inputs (package-propagated-inputs emacs-piem)
         (append emacs-debbugs))))))
--8<---------------cut here---------------end--------------->8---

If you could CC me on the next release, that'd be wonderful; I can
propose an updated guix package expression (and make sure the info
manual is actually built/installed, which it is not currently).

- Jelle

  reply	other threads:[~2023-06-10 23:46 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 ` [PATCH v2 0/5] New piem-debbugs integration jlicht
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 [this message]
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=87zg56anjt.fsf@fsfe.org \
    --to=jlicht@fsfe.org \
    --cc=kyle@kyleam.com \
    --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).