All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] add a counter in grub_dprintf
Date: Tue, 01 Jul 2008 20:13:50 -0400	[thread overview]
Message-ID: <1214957630.7362.2.camel@dv> (raw)
In-Reply-To: <20080701171953.GA9105@thorin>

On Tue, 2008-07-01 at 19:19 +0200, Robert Millan wrote:
> On Tue, Jul 01, 2008 at 12:01:57PM -0400, Pavel Roskin wrote:
> > On Tue, 2008-07-01 at 17:59 +0200, Robert Millan wrote:
> > 
> > > > Adding a complicated mechanism for having debug and non-debug images
> > > > looks like an overkill to me.  It could create more problems than it
> > > > would fix.
> > > 
> > > But then, what do you suggest?  That we remove debug support altogether?
> > 
> > Keep what we have unless we are under pressure to remove it.
> 
> We _are_ under pressure.  Some setups are too big for core.img to fit in
> post-MBR region already.

Then parts of the debugging code that goes into core.img should be good
candidates for removal.  However, we could probably start with lzma
conversion (or did we pick gzip?)

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-07-02  0:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 13:31 [PATCH] add a counter in grub_dprintf Robert Millan
2008-06-19 18:42 ` Isaac Dupree
2008-06-21 14:19   ` Robert Millan
2008-06-21 14:35     ` Javier Martín
2008-06-21 14:51       ` Bram Diederik
2008-06-22 11:30       ` Isaac Dupree
2008-06-26 14:08       ` Robert Millan
2008-06-26 15:20         ` Javier Martín
2008-06-29 11:22           ` Robert Millan
2008-06-30 17:13             ` Pavel Roskin
2008-06-30 17:33               ` Vesa Jääskeläinen
2008-07-01 15:59                 ` Robert Millan
2008-07-01 15:59               ` Robert Millan
2008-07-01 16:01                 ` Pavel Roskin
2008-07-01 17:19                   ` Robert Millan
2008-07-02  0:13                     ` Pavel Roskin [this message]
2008-07-03 18:08 ` Marco Gerards

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=1214957630.7362.2.camel@dv \
    --to=proski@gnu.org \
    --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.