From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: 49181@debbugs.gnu.org
Cc: Leo Prikler <leo.prikler@student.tugraz.at>
Subject: [bug#49181] [PATCH 1/1] guix: Make modify-phases error when adding before/after a missing phase
Date: Wed, 03 Nov 2021 09:58:52 +1100 [thread overview]
Message-ID: <87ilxa5fev.fsf@zancanaro.id.au> (raw)
In-Reply-To: <20210623072509.7165-2-leo.prikler@student.tugraz.at>
This patch has been sitting around for a while, and I think it
would be good to merge it. It still applies cleanly on top of
master.
What can I do to get this merged?
Carlo
On Wed, Jun 23 2021, Leo Prikler wrote:
> From: Carlo Zancanaro <carlo@zancanaro.id.au>
>
> * guix/build/utils.scm (alist-cons-before, alist-cons-after):
> Cause a match failure if the
> reference is not found, rather than appending to the alist.
> * tests/build-utils.scm: Update tests to match.
> ---
> guix/build/utils.scm | 15 +++++++++------
> tests/build-utils.scm | 12 ++++++------
> 2 files changed, 15 insertions(+), 12 deletions(-)
>
> ...
next prev parent reply other threads:[~2021-11-02 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 6:45 [bug#49181] Fix missing phases in Emacs builds Carlo Zancanaro
2021-06-23 7:25 ` [bug#49181] [PATCH 0/1] modify-phases: error when encountering missing phase (was: Fix missing phases in Emacs builds) Leo Prikler
2021-06-23 7:25 ` [bug#49181] [PATCH 1/1] guix: Make modify-phases error when adding before/after a missing phase Leo Prikler
2021-07-23 21:32 ` [bug#49181] Fix missing phases in Emacs builds Sarah Morgensen
2021-11-02 22:58 ` Carlo Zancanaro [this message]
2023-03-29 2:18 ` Maxim Cournoyer
2023-05-20 13:13 ` Carlo Zancanaro
2023-05-20 13:05 ` [bug#49181] [PATCH core-updates v2] guix: Make modify-phases error when adding before/after a missing phase Carlo Zancanaro
2023-10-10 0:50 ` Carlo Zancanaro
2023-10-10 3:37 ` bug#49181: " Maxim Cournoyer
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=87ilxa5fev.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=49181@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).