From: "Ludovic Courtès" <ludo@gnu.org>
To: Mitchell Schmeisser <mitchellschmeisser@librem.one>
Cc: 61765@debbugs.gnu.org
Subject: [bug#61765] custom toolchain blog post
Date: Wed, 15 Mar 2023 15:45:43 +0100 [thread overview]
Message-ID: <87r0tq3wfc.fsf_-_@gnu.org> (raw)
In-Reply-To: <e0a66bab-2bca-cbd2-2e3b-c893c0391a1d@librem.one> (Mitchell Schmeisser's message of "Mon, 13 Mar 2023 09:52:32 -0400")
Hi,
Mitchell Schmeisser <mitchellschmeisser@librem.one> skribis:
> Sorry about the code formatting... Does anyone have any tips for
> getting emacs to format scheme code in markdown?
No tips, other than making sure to untabify. :-)
> From 0f6c28345a51e20004bc16b73bda1c0e5ccb7f4c Mon Sep 17 00:00:00 2001
> From: Mitchell Schmeisser <mitchellschmeisser@librem.one>
> Date: Mon, 13 Mar 2023 09:36:36 -0400
> Subject: [PATCH 1/2] website: custom-toolchains-with-guix: Code fix
>
> * website/drafts/custom-toolchains-with-guix.md: Removed unnecessary
> native-inputs from gcc-arm-zephyr-eabi-toolchain code block.
[...]
> From 25a65c6ace2a3df43d6c3c6d6e23062a51419025 Mon Sep 17 00:00:00 2001
> From: Mitchell Schmeisser <mitchellschmeisser@librem.one>
> Date: Mon, 13 Mar 2023 09:39:22 -0400
> Subject: [PATCH 2/2] website: custom-toolchains-with-guix: Update reference
> URL
>
> * website/drafts/custom-toolchains-with-guix.md: Changed url from
> "latest" to 3.1 which was the current version at the time of writting.
Applied, and finally published:
https://guix.gnu.org/en/blog/2023/building-toolchains-with-guix/
Thank you!
Ludo’.
next prev parent reply other threads:[~2023-03-15 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 18:51 [bug#61765] custom toolchain blog post Mitchell Schmeisser via Guix-patches via
2023-02-27 12:50 ` Ludovic Courtès
2023-02-27 15:35 ` Mitchell Schmeisser via Guix-patches
2023-03-11 12:11 ` Ludovic Courtès
2023-03-11 16:50 ` Mitchell Schmeisser via Guix-patches via
2023-03-13 13:52 ` Mitchell Schmeisser via Guix-patches via
2023-03-15 14:45 ` Ludovic Courtès [this message]
2023-03-16 1:55 ` Mitchell Schmeisser via Guix-patches via
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=87r0tq3wfc.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=61765@debbugs.gnu.org \
--cc=mitchellschmeisser@librem.one \
/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.