all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: 50238@debbugs.gnu.org
Subject: [bug#50238] [PATCH v2] build-self: Try printing nicer error messages
Date: Sun, 27 Mar 2022 22:17:12 +0200	[thread overview]
Message-ID: <2cc17c4b63770ff8d02ff1906d608e86634bd04e.camel@telenet.be> (raw)
In-Reply-To: <ef71cec4d9915f8a1b1dff6d08af7c444fc20caa.camel@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 344 bytes --]

Maxime Devos schreef op di 22-03-2022 om 23:24 [+0100]:
> The revised patch allows time travelling from v1.1.0 to
> (master + patch), by not always setting #:unwind?.  Next step: test
> some older versions (v1.0.0, v0.2?, ...?)?
> 
> Greetings,
> Maxime.

I think the current patch is good enough as-is.  WDYT?

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-03-27 20:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-28 14:36 [bug#50238] [PATCH] build-self: Try printing nicer error messages Maxime Devos
2021-09-24 11:59 ` Ludovic Courtès
2022-03-08 19:22   ` zimoun
2022-03-09 13:18     ` Maxime Devos
2022-03-08 18:58 ` Maxime Devos
2022-03-19  9:13 ` [bug#50238] [PATCH] build-self: Try printing nicer error messages --- verifying if it doesn't break anything Maxime Devos
2022-03-22 20:46   ` Maxime Devos
2022-03-22 20:55     ` Maxime Devos
2022-03-22 20:57     ` Maxime Devos
2022-03-22 22:24 ` [bug#50238] [PATCH v2] build-self: Try printing nicer error messages Maxime Devos
2022-03-27 20:17   ` Maxime Devos [this message]
2022-05-06 12:48 ` [bug#50238] [PATCH] " Maxime Devos
2022-06-13  2:03 ` Maxime Devos
2022-07-09 20:39 ` [bug#50238] Bug in compute-guix-derivation Maxime Devos via Guix-patches
2022-07-30 11:18 ` [bug#50238] [PATCH] build-self: Try printing nicer error messages Maxime Devos
2022-08-13 19:38 ` Maxime Devos

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=2cc17c4b63770ff8d02ff1906d608e86634bd04e.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=50238@debbugs.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.