|
From: | GNU bug Tracking System |
Subject: | bug#53893: closed (Fix non-sequencer from failing to build) |
Date: | Mon, 14 Feb 2022 00:27:02 +0000 |
Your message dated Sun, 13 Feb 2022 19:26:10 -0500 with message-id <YgmhovC4FQSIaF4O@jasmine.lan> and subject line Re: [bug#53893] Fix non-sequencer from failing to build has caused the debbugs.gnu.org bug report #53893, regarding Fix non-sequencer from failing to build to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 53893: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53893 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: Fix non-sequencer from failing to build Date: Wed, 09 Feb 2022 03:46:02 +0000 fix-non-sequencer.patch
Description: Binary data
--- End Message ---
--- Begin Message ---Subject: Re: [bug#53893] Fix non-sequencer from failing to build Date: Sun, 13 Feb 2022 19:26:10 -0500 On Thu, Feb 10, 2022 at 11:18:17AM +0000, sughosha--- via Guix-patches via wrote: > Hi, > > Thanks for considoring this patch. Crediting me as `Sughosha > <sughosha@disroot.org>` would be fine. Okay, I pushed your fix as commit 6bfb3fc1f450c7d618041303d0ff35691b5991c0: https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6bfb3fc1f450c7d618041303d0ff35691b5991c0 > I look forward to learn how to include this while sending the patch. If you use Git to contribute to Guix, then your work will include authorship information as part of the commits that you generate patches from.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |