From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub 2 command : uppermem (patch proposal)
Date: Sat, 7 Feb 2009 23:00:57 +0100 [thread overview]
Message-ID: <20090207220057.GK6343@thorin> (raw)
In-Reply-To: <200901272030.33342.bsd@makefile.in>
On Tue, Jan 27, 2009 at 08:30:32PM -0500, Bandan Das wrote:
> Hello List,
>
> I was going through the Grub 2 TODO here : http://grub.enbug.org/TodoList and
> I see that one of the many commands that need to be implemented is "uppermem".
The text in that list was a bit confusing. We don't have to implement _all_
missing commands, only those we find useful.
> Having played around with uppermem quite a bit (thanks to the weird systems I
> have to work with) on Grub Legacy, I was wondering if a patch for the same
> would be considered for inclusion? Please note that I haven't started work on
> it yet. I wanted to make sure that it's something desirable before putting up
> a patch.
Could you describe your problem in more detail, so we can discuss if it's
something that makes uppermem worthy or we'd rather solve it in some other
way? We don't want to leave your use case out in the cold, only to see if it
can be supported in a better way.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-02-07 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 16:03 Bugfix: no cursor on command line phcoder
2009-01-27 20:47 ` Vesa Jääskeläinen
2009-01-27 20:56 ` phcoder
2009-01-27 21:12 ` Vesa Jääskeläinen
2009-01-28 1:30 ` Grub 2 command : uppermem (patch proposal) Bandan Das
2009-02-07 22:00 ` Robert Millan [this message]
2009-02-09 20:06 ` Bandan
2009-02-21 13:07 ` Robert Millan
2009-01-28 5:18 ` Bugfix: no cursor on command line phcoder
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=20090207220057.GK6343@thorin \
--to=rmh@aybabtu.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 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.