From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 69017@debbugs.gnu.org
Subject: bug#69017: 30.0.50; [debbugs] Make compilation step optional in debbugs-gnu-apply-patch
Date: Sun, 11 Feb 2024 09:18:58 +0100 [thread overview]
Message-ID: <87y1brbeh9.fsf@gmx.de> (raw)
In-Reply-To: <878r3sxcrp.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 10 Feb 2024 12:52:42 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
Hi Eric,
> I've attached the minimum workable approach, which just lets the user
> set the compile command to nil to skip compilation, and the relevant
> window rearrangements afterwards.
Looks OK in general. You need to adapt the :type of
debbugs-gnu-compile-command, and also to add some few words about in
debbugs-ug.texi.
Best regards, Michael.
next prev parent reply other threads:[~2024-02-11 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 17:42 bug#69017: 30.0.50; [debbugs] Make compilation step optional in debbugs-gnu-apply-patch Eric Abrahamsen
2024-02-10 18:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-10 19:23 ` Eric Abrahamsen
2024-02-10 19:27 ` Eli Zaretskii
2024-02-10 19:58 ` Eric Abrahamsen
2024-02-10 20:26 ` Eli Zaretskii
2024-02-10 20:52 ` Eric Abrahamsen
2024-02-11 8:18 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-11 15:05 ` Eric Abrahamsen
2024-02-11 15:43 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-16 5:50 ` Eric Abrahamsen
2024-02-11 8:11 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-11 15:05 ` Eric Abrahamsen
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=87y1brbeh9.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=69017@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eric@ericabrahamsen.net \
--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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.