From: "Ludovic Courtès" <ludo@gnu.org>
To: Tomas Volf <~@wolfsden.cz>
Cc: 68505-done@debbugs.gnu.org
Subject: bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file.
Date: Mon, 29 Jan 2024 14:27:32 +0100 [thread overview]
Message-ID: <87v87cp8vv.fsf_-_@gnu.org> (raw)
In-Reply-To: <20240124165526.19035-1-~@wolfsden.cz> (Tomas Volf's message of "Wed, 24 Jan 2024 17:48:04 +0100")
Tomas Volf <~@wolfsden.cz> skribis:
> Until now, the ./meta/guile was not mentioned anywhere, and therefore it
> was not obvious how to run the locally compiled Guile without installing
> it.
>
> While modifying the file, I took the liberty to also mention a bit about
> compiling Guile using Guix.
>
> Finally, the header lines where cleaned up, ensuring all of them end at
> 70 and have a leading space.
>
> * HACKING (Hacking It Yourself): Add Guix instructions. Add a note
> about meta/guile script.
> (Sample GDB Initialization File),
> (Naming conventions): Clean up the header line.
Applied, thanks!
prev parent reply other threads:[~2024-01-29 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 12:50 bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file Tomas Volf
2024-01-24 10:18 ` Ludovic Courtès
2024-01-24 16:59 ` Tomas Volf
2024-01-24 16:48 ` bug#68505: [PATCH v3] " Tomas Volf
2024-01-29 13:27 ` Ludovic Courtès [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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v87cp8vv.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=68505-done@debbugs.gnu.org \
--cc=~@wolfsden.cz \
/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).