all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39414@debbugs.gnu.org
Subject: [bug#39414] [PATCH 1/2] gnu: commencement: Avoid hard-coded GCC version numbers.
Date: Thu, 06 Feb 2020 07:16:54 +0100	[thread overview]
Message-ID: <875zgk5jft.fsf@gnu.org> (raw)
In-Reply-To: <20200204130042.27757-1-ludo@gnu.org> ("Ludovic \=\?utf-8\?Q\?Cou\?\= \=\?utf-8\?Q\?rt\=C3\=A8s\=22's\?\= message of "Tue, 4 Feb 2020 14:00:41 +0100")

Ludovic Courtès writes:

> * gnu/packages/commencement.scm (gcc-mesboot1, gcc-mesboot): Use
> 'package-version' instead of hard-coding the version number.

Makes sense, LGTM.
janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

  parent reply	other threads:[~2020-02-06  6:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 12:53 [bug#39414] [PATCH core-updates 0/2] Clarify search path handling in commencement.scm Ludovic Courtès
2020-02-04 13:00 ` [bug#39414] [PATCH 1/2] gnu: commencement: Avoid hard-coded GCC version numbers Ludovic Courtès
2020-02-04 13:00   ` [bug#39414] [PATCH 2/2] gnu: commencement: Rationalize search path handling Ludovic Courtès
2020-02-06  6:25     ` Jan Nieuwenhuizen
2020-02-06 14:22       ` Ludovic Courtès
2020-02-06 17:48         ` bug#39414: " Ludovic Courtès
2020-02-06  6:16   ` Jan Nieuwenhuizen [this message]
2020-02-06  6:39 ` [bug#39414] [PATCH core-updates 0/2] Clarify search path handling in commencement.scm Jan Nieuwenhuizen
2020-02-06 14:25   ` Ludovic Courtès

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=875zgk5jft.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=39414@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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.