From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [RFC][PATCH] Allow hotkeys to interrupt hidden menu
Date: Fri, 29 Nov 2013 10:21:40 +0400 [thread overview]
Message-ID: <20131129102140.64a0cdf6@opensuse.site> (raw)
In-Reply-To: <20131128180644.GB16321@riva.ucam.org>
В Thu, 28 Nov 2013 18:06:44 +0000
Colin Watson <cjwatson@ubuntu.com> пишет:
> On Thu, Nov 28, 2013 at 09:22:49PM +0400, Andrey Borzenkov wrote:
> > В Thu, 28 Nov 2013 02:30:56 +0000
> > Colin Watson <cjwatson@ubuntu.com> пишет:
> > > @item GRUB_HIDDEN_TIMEOUT
> > > @item GRUB_HIDDEN_TIMEOUT_QUIET
> >
> > I suggest removing them from user visible documentation and leaving
> > only as compatibility options in grub-mkconfig. No reason do endorse
> > their usage ("deprecated" is usually was nobody pays attention to).
>
> My concern is that they will probably hang around in people's
> configurations for some time and I would like the documentation to tell
> users what these mysterious things mean.
>
> As a compromise, perhaps we could move them to a separate page?
>
May be collect all deprecated options at the end of list with heading
like "The following options are still accepted for compatibility with
existing configurations but should not be used in new setup anymore" or
similar.
And BTW, we probably need to start collecting NEWS topics - this is
excellent candidate for inclusion :)
next prev parent reply other threads:[~2013-11-29 6:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 13:18 [RFC][PATCH] Allow hotkeys to interrupt hidden menu Colin Watson
2013-09-11 13:31 ` Colin Watson
2013-09-12 2:40 ` Andrey Borzenkov
2013-09-13 9:18 ` Franz Hsieh
2013-09-19 6:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-02 8:03 ` Franz Hsieh
2013-10-02 8:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-14 6:02 ` Franz Hsieh
2013-10-21 6:45 ` Franz Hsieh
2013-11-04 3:10 ` Yang Bai
2013-11-27 23:40 ` Colin Watson
2013-11-28 2:30 ` Colin Watson
2013-11-28 6:19 ` Vladimir 'phcoder' Serbinenko
2013-11-28 11:04 ` Colin Watson
2013-11-28 14:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-29 16:18 ` Colin Watson
2013-11-29 16:56 ` Andrey Borzenkov
2013-11-29 17:20 ` Colin Watson
2013-11-29 17:29 ` [PATCH] document sleep command exit codes Andrey Borzenkov
2013-11-30 10:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-28 17:20 ` [RFC][PATCH] Allow hotkeys to interrupt hidden menu Andrey Borzenkov
2013-11-28 18:05 ` Colin Watson
2013-11-29 6:17 ` Andrey Borzenkov
2013-11-29 15:26 ` Colin Watson
2013-11-28 17:22 ` Andrey Borzenkov
2013-11-28 18:06 ` Colin Watson
2013-11-29 6:21 ` Andrey Borzenkov [this message]
2013-09-12 2:44 ` Andrey Borzenkov
2013-09-12 13:17 ` Colin Watson
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=20131129102140.64a0cdf6@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).