All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] add true and false commands
Date: Fri, 05 Jun 2009 15:29:21 +0200	[thread overview]
Message-ID: <87vdnax0zy.fsf@xs4all.nl> (raw)
In-Reply-To: <1244207062.3416.45.camel@fz.local> (Felix Zielcke's message of "Fri, 05 Jun 2009 15:04:22 +0200")

Felix Zielcke <fzielcke@z-51.de> writes:

> Am Freitag, den 05.06.2009, 14:26 +0200 schrieb Marco Gerards:
>> Felix Zielcke <fzielcke@z-51.de> writes:
>
>> > So what should I do now?
>> > Placing it in normal.mod or minicmd.mod where it's included in rescue
>> > mode or placing it into a true.mod where the size increase would be
>> > bigger?
>> 
>> minicmd.mod is not a very descriptive name.  Better call is
>> truefalse.mod or something like that.
>
> minicmd.mod already exists, see commands/minicmd.c (or my first patch).
> That's where I put it in the first patch.
> Anyway here's a new one which adds true.mod which gets 1264 bytes big.

Oh, I didn't know minicmd.mod.  Is it useful to have one instead of
a few separate modules?  Space of these smaller modules is not really
a concern to me.

--
Marco




  reply	other threads:[~2009-06-05 13:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 12:16 [PATCH] add true and false commands Felix Zielcke
2009-05-30 15:14 ` Vladimir 'phcoder' Serbinenko
2009-06-01 14:18   ` Felix Zielcke
2009-06-01 14:24     ` Vladimir 'phcoder' Serbinenko
2009-06-03 15:45       ` Felix Zielcke
2009-06-04  8:21         ` Marco Gerards
2009-06-05  8:47           ` Felix Zielcke
2009-06-05 10:00             ` Marco Gerards
2009-06-05 10:32               ` Felix Zielcke
2009-06-05 12:26                 ` Marco Gerards
2009-06-05 13:04                   ` Felix Zielcke
2009-06-05 13:29                     ` Marco Gerards [this message]
2009-06-05 15:56                       ` Felix Zielcke
2009-06-08  7:32                     ` Felix Zielcke

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=87vdnax0zy.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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 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.