Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: RFC: conf/i386.rmk
Date: Tue, 5 Aug 2008 22:07:15 +0200	[thread overview]
Message-ID: <20080805200715.GA1113@thorin> (raw)
In-Reply-To: <1217954986.2722.4.camel@dv>

On Tue, Aug 05, 2008 at 12:49:46PM -0400, Pavel Roskin wrote:
> On Tue, 2008-08-05 at 09:58 +0300, Vesa Jääskeläinen wrote:
> 
> > > I tried moving more stuff to common.rmk many times but gave up every
> > > time.  One of the reasons is that the sparc64 support is very
> > > out-of-date and doesn't use common.rmk at all.  I cannot even test it
> > > (well, I haven't tries hard).
> > 
> > If sparc64 support is out of date and the maintainer is nowhere to be 
> > seen then I think you can put that support to graveyard until someone 
> > comes up to update it. Putting all common stuff to every platform to 
> > common.rmk is a good way and the only way (in my opinion) to go forward.
> 
> OK, then there is an issue that it doesn't work if done naively.

What is the problem exactly?

-- 
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."



  reply	other threads:[~2008-08-05 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 19:28 RFC: conf/i386.rmk Robert Millan
2008-08-03 19:30 ` Robert Millan
2008-08-04  4:59   ` Pavel Roskin
2008-08-05  6:58     ` Vesa Jääskeläinen
2008-08-05 16:49       ` Pavel Roskin
2008-08-05 20:07         ` Robert Millan [this message]
2008-08-05 21:08           ` Pavel Roskin
2008-09-05 10:54             ` [PATCH] Move cpuid.mod to conf/i386.rmk (Re: RFC: conf/i386.rmk) Robert Millan
2008-09-07 17:13               ` Robert Millan
2008-08-04 22:08   ` RFC: conf/i386.rmk 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=20080805200715.GA1113@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox