unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Bruno Haible <bruno@clisp.org>, 41038@debbugs.gnu.org
Subject: bug#41038: [PATCH] doc: Reword "The GCC toolchain".
Date: Fri, 15 May 2020 21:42:17 +0200	[thread overview]
Message-ID: <873681x9wm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJ3okZ2AYjiFRZnr1VZo+_OOjysEgwcZWwJo9hjmBe15ayc=8A@mail.gmail.com> (zimoun's message of "Wed, 6 May 2020 19:42:09 +0200")

Hello,

zimoun <zimon.toutoune@gmail.com> writes:

> See attached.  Feel free to reword the commit message if it is not
> compliant with the standard.

I have two minor comments about it.

> +The package @code{gfortran-toolchain} provides a complete GCC toolchain
> +for Fortran development.  For other languages, please use
> +@command{guix search gcc toolchain}

Nitpick: I know there is plenty of this in the manual, but I suggest to
use @samp{guix ...}, not @command{...}.

> (see @pxref{guix-search,, Invoking guix package}).

You need to remove the "see ":

  (@pxref{...})


Regards,

-- 
Nicolas Goaziou




  parent reply	other threads:[~2020-05-15 19:43 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 [this message]
2020-05-16 14:57               ` zimoun
2020-05-16 15:19                 ` Ludovic Courtès
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=873681x9wm.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=41038@debbugs.gnu.org \
    --cc=bruno@clisp.org \
    --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).