From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Bruno Haible <bruno@clisp.org>,
41038@debbugs.gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: bug#41038: [PATCH] doc: Reword "The GCC toolchain".
Date: Sat, 16 May 2020 17:19:54 +0200 [thread overview]
Message-ID: <87o8qnsy91.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ35qSS21_E0pdhT9SVV7xUibobzhXmNYtt+9ESjxr=gww@mail.gmail.com> (zimoun's message of "Sat, 16 May 2020 16:57:11 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> From efbc579a8884235ac37833ea6ee6fa454110c080 Mon Sep 17 00:00:00 2001
> From: zimoun <zimon.toutoune@gmail.com>
> Date: Wed, 6 May 2020 19:26:05 +0200
> Subject: [PATCH v2] doc: Reword "The GCC toolchain".
>
> Fix commit 1f14e25c1969a93908288cb302a572f3cbbaa478
> as discussed in <https://bugs.gnu.org/41038>.
>
> * doc/guix.texi (Packages for C Development): Rename to...
> (The GCC toolchain): ...this. Add gfortran-toolchain.
> (Invoking guix package): Add guix-search anchor.
> (Application Setup)[The GCC toolchain]: Remove.
Applied, thanks!
Ludo’.
next prev parent reply other threads:[~2020-05-16 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 23:55 bug#41038: gcc creates binaries that don't find their shared libraries Bruno Haible
2020-05-03 21:07 ` Ludovic Courtès
2020-05-03 23:09 ` Bruno Haible
2020-05-04 8:50 ` zimoun
2020-05-04 9:06 ` zimoun
2020-05-04 9:30 ` Ludovic Courtès
2020-05-04 9:59 ` zimoun
2020-05-04 19:52 ` Ludovic Courtès
2020-05-06 17:42 ` bug#41038: [PATCH] doc: Reword "The GCC toolchain" zimoun
2020-05-15 16:59 ` zimoun
2020-05-15 19:42 ` Nicolas Goaziou
2020-05-16 14:57 ` zimoun
2020-05-16 15:19 ` Ludovic Courtès [this message]
2020-05-03 22:12 ` bug#41038: gcc creates binaries that don't find their shared libraries Danny Milosavljevic
2020-05-05 9:30 ` Ludovic Courtès
2020-05-05 11:17 ` Bruno Haible
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8qnsy91.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41038@debbugs.gnu.org \
--cc=bruno@clisp.org \
--cc=mail@nicolasgoaziou.fr \
--cc=zimon.toutoune@gmail.com \
/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/guix.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).