From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Prarit Bhargava <prarit@redhat.com>, cjwatson@ubuntu.com
Subject: Re: [PATCH] Clarify "Press any key to continue..." message
Date: Thu, 3 Apr 2014 21:15:45 +0400 [thread overview]
Message-ID: <20140403211545.7fc266ec@opensuse.site> (raw)
In-Reply-To: <20140403165257.GU32733@riva.ucam.org>
В Thu, 3 Apr 2014 17:52:57 +0100
Colin Watson <cjwatson@ubuntu.com> пишет:
>
> Seems like a lot of effort. The actual delay is 2.5 seconds
May be I misunderstand it, but how 10000ms becomes 2.5 seconds?
next prev parent reply other threads:[~2014-04-03 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 14:23 [PATCH] Clarify "Press any key to continue..." message Colin Watson
2014-04-03 16:49 ` Prarit Bhargava
2014-04-03 16:52 ` Colin Watson
2014-04-03 16:57 ` Prarit Bhargava
2014-04-03 17:11 ` Colin Watson
2014-04-03 17:15 ` Andrey Borzenkov [this message]
2014-04-07 17:25 ` Colin Watson
2014-07-23 7:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20140403211545.7fc266ec@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=cjwatson@ubuntu.com \
--cc=grub-devel@gnu.org \
--cc=prarit@redhat.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.
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).