From: Michael Albinus <michael.albinus@gmx.de>
To: Joshua Branson <jbranso@dismail.de>
Cc: help-gnu-emacs@gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: Use Debbugs to search for only open bugs
Date: Wed, 10 Aug 2022 18:23:56 +0200 [thread overview]
Message-ID: <87wnbgdq3n.fsf@gmx.de> (raw)
In-Reply-To: <87lerwp1by.fsf@dismail.de> (Joshua Branson's message of "Wed, 10 Aug 2022 11:25:53 -0400")
Joshua Branson <jbranso@dismail.de> writes:
[Adding Lars to Cc, the coauthor of the debbugs package]
> Also, the reason I was asking the help-gnu-emacs list, was that I have a
> pending guix patch see bug 56987, that provides the following functions
> in guix's etc/ directory.
>
> debbugs-guix-search (by default searching for open open bugs)
>
> debbugs-my-open-bugs (by default search for only open bugs that the
> user has submitted)
>
> debbugs-get-bug-by-id (fairly obvious)
>
> It might actually make more sense for these patches to be merged into
> upstream debbugs. Perhaps by changing the names:
>
> debbugs-gnu-guix-search
>
> debbugs-gnu-my-open-bugs
>
> debbugs-gnu-get-buy-by-id
>
> What do you think?
Yea, would be possible. The first function could live in a file
debbugs-guix.el, the other two function might enter
debbugs-gnu.el. There's one formal restriction: debbugs is part of the
GNU ELPA repository, which requires the authors to give the copyright to
FSF, and to sign the legal papers. Would you be willing to do so?
I guess further discussion could happen on bug#56987.
> Joshua
Best regards, Michael.
prev parent reply other threads:[~2022-08-10 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 19:40 Use Debbugs to search for only open bugs Joshua Branson
2022-08-05 1:25 ` Michael Heerdegen
2022-08-05 7:08 ` Michael Albinus
2022-08-05 8:55 ` Joshua Branson
2022-08-05 9:46 ` Michael Albinus
2022-08-10 13:54 ` Michael Albinus
2022-08-10 15:17 ` Joshua Branson
2022-08-10 15:25 ` Joshua Branson
2022-08-10 16:23 ` Michael Albinus [this message]
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnbgdq3n.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=jbranso@dismail.de \
--cc=larsi@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 read-only IMAP folder(s) and NNTP newsgroup(s).