From: Joshua Branson via Guix-patches via <guix-patches@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 56987@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: [bug#56987] [PATCH] etc: guix-debbugs.el: new file.
Date: Thu, 11 Aug 2022 11:25:45 -0400 [thread overview]
Message-ID: <87zggaol8m.fsf@dismail.de> (raw)
In-Reply-To: <87wnbfpaa9.fsf@gmx.de> (Michael Albinus's message of "Thu, 11 Aug 2022 08:24:46 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> jbranso@dismail.de writes:
>
> Hi Joshua,
>
>> I am willing to submit copyright assignment to GNU/FSF. It looks like the FSF
>> has a webpage that may make this process easier:
>>
>> https://sfconservancy.org/assignment/
>>
>> Should I use that web page to submit my potential copyright assignment?
>
> No, you need the FSF template. Sent offlist.
>
>>>> @example
>>>> @kbd{C-u} @kbd{M-x} debbugs-gnu @kbd{RET} @kbd{RET} guix-patches @kbd{RET} n y
>>>> @end example
>>>
>>> Alternatively, a user could set debbugs-gnu-default-packages to '("guix" "guix-patches")
>>> Then it won't be necessary to enter the package name(s) again and again.
>>
>> I think that I have tried that in my config, and I could not get it to work.
>>
>> I will try again and get back to you, and update the guix documentation accordingly.
>
> Well, debbugs-gnu-default-packages isn't used for
> debbugs-gnu-search. But since you are writing about the debbugs package
> in general, the hint might still be useful.
May I ask why debbugs-gnu-search chooses not to use
debbugs-gnu-default-packages? I don't understand. What functions do
use debbugs-gnu-default-packages? Also note, that my experience with
debbugs is REALLY minimal. I haven't even properly read the
manual...I've only skimmed. So maybe I should read it before developing
an opinion. :)
>>> debbugs.el uses a cache, which flushes the value after an hour. See the
>>> variable debbugs-cache-expiry.
>>
>> Maybe, we could mark a bug as done in the cache when one closes the bug via
>> debbugs. That may be a little above my paygrade though.
>
> That's a hazardous way. Bugs are not only closed, but changed in many
> ways. And you don't know, whether a user sends the control message she
> has started to compose.
That's true.
> In debbugs-gnu-make-control-message, a bug is already removed from the
> cache when the control message is sent. This is good enough I believe.
Now that is helpful! so debbugs-gnu-make-control-message assumes that
you are closing the bug. ok. Thanks for the help again Michael! I
couldn't have written this patch this quickly without your help. Heck
you helped me write quite a bit of it!
> Next time the bug data are needed, the data for this bug are fetched
> from the server. However, you must be a little bit patient, when you
> retrieve the data immediately after sending the control message, the
> server might not be ready with the action, and it might send the
> unchanged data.
>
> Best regards, Michael.
next prev parent reply other threads:[~2022-08-11 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 1:23 [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
2022-08-05 1:32 ` Joshua Branson via Guix-patches via
2022-08-10 15:16 ` Joshua Branson via Guix-patches via
2022-08-10 16:44 ` Michael Albinus
2022-08-10 20:10 ` jbranso--- via Guix-patches via
2022-08-10 20:24 ` Maxime Devos
2022-08-10 20:39 ` jbranso--- via Guix-patches via
2022-08-10 21:22 ` [bug#56987] Requesting help in assigning copright to Emacs's debbugs jbranso--- via Guix-patches via
2022-08-11 19:51 ` [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
[not found] ` <304e6f0d877d6b8bb60db051e661edf1@dismail.de>
2022-08-17 20:14 ` [bug#56987] Fwd: [gnu.org #1863422] Joshua Allen Branson GNU EMACS jbranso--- via Guix-patches via
2022-08-18 9:52 ` Michael Albinus
2022-08-22 17:21 ` [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
2022-08-11 6:24 ` Michael Albinus
2022-08-11 15:25 ` Joshua Branson via Guix-patches via [this message]
2022-08-11 16:06 ` Michael Albinus
2022-08-13 22:49 ` Joshua Branson via Guix-patches via
2022-08-12 19:17 ` jbranso--- via Guix-patches via
2022-10-01 15:39 ` [bug#56987] [PATCH] added *my-open-bugs functions Joshua Branson via Guix-patches via
2022-10-02 12:52 ` Michael Albinus
2022-10-03 20:02 ` jbranso--- via Guix-patches via
2022-10-04 14:15 ` Michael Albinus
2022-10-05 16:41 ` [bug#56987] [PATCH] new functions 'debbugs-gnu-my-open-bugs' and 'debbugs-gnu-guix-search' Joshua Branson via Guix-patches via
2022-10-05 20:10 ` bug#56987: " Michael Albinus
[not found] <rt-4.2.16-14-g9a593ee-12923-1660753466-248.1863422-5-0@rt.gnu.org>
[not found] ` <RT-Ticket-1863422@rt.gnu.org>
[not found] ` <rt-4.2.16-14-g9a593ee-21845-1660236515-917.1863103-5-0@rt.gnu.org>
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=87zggaol8m.fsf@dismail.de \
--to=guix-patches@gnu.org \
--cc=56987@debbugs.gnu.org \
--cc=jbranso@dismail.de \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.