From: Vagrant Cascadian <vagrant@debian.org>
To: 31159@debbugs.gnu.org
Subject: bug#31159: #31159: Reverse order for old grub.cfg entries
Date: Thu, 31 May 2018 15:07:22 -0700 [thread overview]
Message-ID: <87muwfqy1x.fsf@aikidev.net> (raw)
In-Reply-To: <handler.31159.C.152775849827440.notifdonectrl.0@debbugs.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
On 2018-05-31, GNU bug Tracking System wrote:
> This is an automatic notification regarding your bug report
> #31159: Reverse order for old grub.cfg entries,
> which was filed against the guix package.
>
> Thank you for your report, which has now been closed.
> You can view the full report at
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31159
I don't see that the proposed patch was applied to any of the guix
branches I'm aware of. Has it been merged and just not yet been pushed?
Does it need to go to guix-patches instead of guix-bugs?
Thanks!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-05-31 22:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r2lsji3l.fsf@lassieur.org>
2018-04-15 3:20 ` bug#31159: Reverse order for old grub.cfg entries Vagrant Cascadian
2018-04-15 17:22 ` Joshua Branson
2018-04-16 14:33 ` Mark H Weaver
2018-04-17 8:16 ` Mathieu Othacehe
2018-04-17 18:18 ` Mark H Weaver
2018-04-18 14:04 ` Ludovic Courtès
2018-04-18 19:23 ` Mark H Weaver
2018-04-18 20:14 ` Ludovic Courtès
2018-04-19 15:21 ` Mathieu Othacehe
2018-04-23 15:16 ` Ludovic Courtès
[not found] ` <handler.31159.C.152775849827440.notifdonectrl.0@debbugs.gnu.org>
2018-05-31 22:07 ` Vagrant Cascadian [this message]
2018-06-01 2:18 ` bug#31159: #31159: " Mark H Weaver
2018-06-01 7:46 ` Mathieu Othacehe
2018-06-01 7:46 ` Mathieu Othacehe
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=87muwfqy1x.fsf@aikidev.net \
--to=vagrant@debian.org \
--cc=31159@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.