From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] break command support
Date: Sun, 09 May 2010 15:13:09 +0200 [thread overview]
Message-ID: <4BE6B4E5.9050209@gmail.com> (raw)
In-Reply-To: <g2pd019d53c1005050341q742954dl191748df5e6203ea@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Other than a comment about the case n> active_loops it can go into exp
BVK Chaitanya wrote:
> Hi,
>
>
> Attached patch adds "break [n]" command support to GRUB script. This
> needs to be applied on top of func-params patch.
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
prev parent reply other threads:[~2010-05-09 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 10:41 [PATCH] break command support BVK Chaitanya
2010-05-05 18:01 ` Seth Goldberg
2010-05-07 6:07 ` BVK Chaitanya
2010-05-09 13:13 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4BE6B4E5.9050209@gmail.com \
--to=phcoder@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