From: jbranso--- via Guix-patches via <guix-patches@gnu.org>
To: "Michael Albinus" <michael.albinus@gmx.de>
Cc: 56987@debbugs.gnu.org
Subject: [bug#56987] [PATCH] added *my-open-bugs functions
Date: Mon, 03 Oct 2022 20:02:38 +0000 [thread overview]
Message-ID: <60925dca97526a602e2ca2c140beca45@dismail.de> (raw)
In-Reply-To: <877d1icrrc.fsf@gmx.de>
October 2, 2022 8:52 AM, "Michael Albinus" <michael.albinus@gmx.de> wrote:
> Joshua Branson <jbranso@dismail.de> writes:
>
> Hi Joshua,
>
>> * debbugs-gnu.el: debbugs-gnu-my-open-bugs: new procedure.
>> * debbugs-org.el: debbugs-org-my-open-bugs: new procedure.
>> * debbugs-guix.el: debbugs-gnu-guix-search: new procedure.
>> * debugs-ug.texi: added documentation for *my-open-bugs procedures.
>
> Thanks for this. In order to push the changes, I'd like to get ChangeLog
> like commit messages.
I thought that's what I had. I'll try to fix it. I'll just look at
the git history.
>
> debbugs-gnu-my-open-bugs and debbugs-org-my-open-bugs are explained in
> the UG. But since not everybody reads manuals, we explain the
> interactive commands also in the Commentary section of the respective
> file. Could you please do?
>
Yes will do.
>> I did not actually compile the debbugs-ug.text, so it is possible that my
>> documentation makes the info program impossible to compile.
>
> It compiles, but the reference to the Emacs manual is wrong. Better
> would be
>
> --8<---------------cut here---------------start------------->8---
> (@pxref{Mail Headers, , , emacs}).
> --8<---------------cut here---------------end--------------->8---
>
> It also wouldn't hurt if you add a small section about
> debbugs-gnu-guix-search. Everything, what is undocumenbted, doesn't
> exist :-)
I will do both points. Should every interactive function in any *.el file
have an autoload ?
>
>> Thanks,
>>
>> Joshua
>
> Best regards, Michael.
next prev parent reply other threads:[~2022-10-03 20:34 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
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 [this message]
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=60925dca97526a602e2ca2c140beca45@dismail.de \
--to=guix-patches@gnu.org \
--cc=56987@debbugs.gnu.org \
--cc=jbranso@dismail.de \
--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.