all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 31159@debbugs.gnu.org
Subject: bug#31159: Reverse order for old grub.cfg entries
Date: Mon, 16 Apr 2018 10:33:56 -0400	[thread overview]
Message-ID: <87y3hnnru3.fsf@netris.org> (raw)
In-Reply-To: <87h8odb1fo.fsf@aikidev.net> (Vagrant Cascadian's message of "Sat, 14 Apr 2018 20:20:27 -0700")

Vagrant Cascadian <vagrant@debian.org> writes:

> This is a pretty minor issue, but I've found that the "GNU system, old
> configurations..." part of the menu would be nicer if the most recent
> generations were listed at the top, rather than the oldest generations.
>
> Currently it lists generation 1 as the first entry in the list, and if
> I've got 50+ generations installed and I don't want to boot the current
> generation, I'm most likely going to want to revert to one of the more
> recent generations rather than the very oldest.

I agree that it would be better to reverse the order of these entries.

    Thanks,
      Mark

  parent reply	other threads:[~2018-04-16 14:35 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 [this message]
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     ` bug#31159: #31159: " Vagrant Cascadian
2018-06-01  2:18       ` 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=87y3hnnru3.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=31159@debbugs.gnu.org \
    --cc=vagrant@debian.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.