From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: 49181@debbugs.gnu.org, Leo Prikler <leo.prikler@student.tugraz.at>
Subject: [bug#49181] Fix missing phases in Emacs builds
Date: Tue, 28 Mar 2023 22:18:36 -0400 [thread overview]
Message-ID: <87cz4s47wj.fsf_-_@gmail.com> (raw)
In-Reply-To: <87ilxa5fev.fsf@zancanaro.id.au> (Carlo Zancanaro's message of "Wed, 03 Nov 2021 09:58:52 +1100")
Hi Carlo,
Carlo Zancanaro <carlo@zancanaro.id.au> writes:
> 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?
Have you seen the good comments from Sarah up thread? Perhaps you could
send a rebased v2 integrating them.
And then ping us in #guix if it falls into the cracks again!
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-03-29 2:19 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 ` [bug#49181] [PATCH 1/1] guix: Make modify-phases error when adding before/after a missing phase Carlo Zancanaro
2023-03-29 2:18 ` Maxim Cournoyer [this message]
2023-05-20 13:13 ` [bug#49181] Fix missing phases in Emacs builds 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz4s47wj.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=49181@debbugs.gnu.org \
--cc=carlo@zancanaro.id.au \
--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 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.