From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Pierre Langlois <pierre.langlois@gmx.com>, 59913-done@debbugs.gnu.org
Subject: bug#59913: [tentative PATCH] Failure to guix pull on aarch64 since recent make-linux-libre*
Date: Fri, 13 Jan 2023 16:04:54 -0500 [thread overview]
Message-ID: <878ri6f8nd.fsf@gmail.com> (raw)
In-Reply-To: <87fsdjy6ja.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Tue, 13 Dec 2022 10:52:41 +0100")
Hello,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Pierre Langlois <pierre.langlois@gmx.com> skribis:
>
>> I'm not sure I follow, I'd suggest to revert the revert and then apply a
>> fix in the same commit, that way it can easily be reverted again if it's
>> problematic, that's probably what you meant already?
>
> Sounds good to me. The commit log can be similar to the original one
> (rather than “Revert: "Revert: "whatever"”), with a couple of lines
> like:
>
> This restores commit XYZ, with an additional fix for …
>
> Fixes <https://issues.guix.gnu.org/59913>.
Commit restored as 4913ac74915c4229aeb3ca26a5f9920c759fb6a3, with
Pierre's fix (thanks!)
Closing.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-01-13 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167059225344.15591.17976801315617510996@vcs2.savannah.gnu.org>
2022-12-09 19:18 ` bug#59913: branch master updated: Revert "gnu: make-linux-libre*: Remove input labels." Pierre Langlois
2022-12-09 20:06 ` Maxim Cournoyer
2022-12-09 21:33 ` Pierre Langlois
2022-12-13 9:52 ` bug#59913: [tentative PATCH] Failure to guix pull on aarch64 since recent make-linux-libre* Ludovic Courtès
2023-01-13 21:04 ` Maxim Cournoyer [this message]
2022-12-08 23:31 Pierre Langlois
2022-12-08 23:59 ` Pierre Langlois
2022-12-09 0:36 ` Pierre Langlois
2023-01-13 15:39 ` 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=878ri6f8nd.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=59913-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=pierre.langlois@gmx.com \
/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.