all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 52164@debbugs.gnu.org
Subject: [bug#52164] [PATCH] gnu: coq: Update to 8.14.0.
Date: Mon, 29 Nov 2021 15:13:47 +0100	[thread overview]
Message-ID: <CAJ3okZ31+VdRSe=z4nBcCQk7NXuwozK82Jnd2H-Nbk5p_-E=sg@mail.gmail.com> (raw)
In-Reply-To: <89F34741-9EFC-4C19-8167-3B990D90533F@lepiller.eu>

Re,

On Mon, 29 Nov 2021 at 14:39, Julien Lepiller <julien@lepiller.eu> wrote:

> I've always updated dependents first whenever possible (without breaking anything), then the compiler, then the rest that needs the new compiler. However, I've always been careful not to introduce breakage with a commit, even if it's inside a series. I think that's the policiy, but I'm not sure if it overrides the one-change per commit policy.

Me neither. :-)
Anyway, all LGTM except wrong commit message for coq-semantics.

Cheers,
simon




  reply	other threads:[~2021-11-29 14:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 16:44 [bug#52164] [PATCH] gnu: coq: Update to 8.14.0 Julien Lepiller
2021-11-28 17:27 ` [bug#52164] [PATCH 1/3] gnu: ocaml-semantics: " Julien Lepiller
2021-11-29  9:05   ` zimoun
2021-11-28 17:27 ` [bug#52164] [PATCH 2/3] gnu: proof-general: Update to latest commit Julien Lepiller
2021-11-29  9:06   ` [bug#52164] [PATCH] gnu: coq: Update to 8.14.0 zimoun
2021-11-28 17:27 ` [bug#52164] [PATCH 3/3] " Julien Lepiller
2021-11-29  9:42   ` [bug#52164] [PATCH] " zimoun
2021-11-29 12:29     ` Julien Lepiller
2021-11-29 13:21       ` zimoun
2021-11-29 13:39         ` Julien Lepiller
2021-11-29 14:13           ` zimoun [this message]
2022-05-03 12:35 ` bug#52164: " zimoun

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='CAJ3okZ31+VdRSe=z4nBcCQk7NXuwozK82Jnd2H-Nbk5p_-E=sg@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=52164@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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.