From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 72464@debbugs.gnu.org
Subject: bug#72464: [PATCH 0/2] Add instructions how setup path to C source code for SUSE based systems and improve Red Hat ones
Date: Sun, 04 Aug 2024 19:29:56 +0300 [thread overview]
Message-ID: <86r0b4qmij.fsf@gnu.org> (raw)
In-Reply-To: <87ikwgb7p3.fsf@> (bug-gnu-emacs@gnu.org)
merge 72464 72465 72466
thanks
> Date: Sun, 4 Aug 2024 18:56:15 +0300
> From: Björn Bidar via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> I noticed that there are no instructions how setup the path to C source
> code of Emacs for SUSE based systems.
> These patches add the instructions and improve the instructions for Red Had based
> systems.
>
> Björn Bidar (2):
> Document how set path to C source code for SUSE based systems
> Improve instructions how set path to C source code for Red Hat
>
> etc/PROBLEMS | 21 ++++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
As explained earlier, the way you sent this created 3 separate bug
reports, so I'm now merging them together.
next prev parent reply other threads:[~2024-08-04 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ikwgb7p3.fsf@>
2024-08-04 13:09 ` bug#72464: [PATCH 1/2] Document how set path to C source code for SUSE based systems Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 13:17 ` bug#72464: [PATCH 2/2] Improve instructions how set path to C source code for Red Hat Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 16:29 ` Eli Zaretskii [this message]
2024-08-04 15:56 bug#72464: [PATCH 0/2] Add instructions how setup path to C source code for SUSE based systems and improve Red Hat ones Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86r0b4qmij.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72464@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).