From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: powerpc/sparc problems
Date: Mon, 12 Oct 2009 11:42:25 +0200 [thread overview]
Message-ID: <1255340545.3204.33.camel@fz.local> (raw)
In-Reply-To: <20091012.020508.00113728.davem@davemloft.net>
Am Montag, den 12.10.2009, 02:05 -0700 schrieb David Miller:
> From: Felix Zielcke <fzielcke@z-51.de>
> Date: Mon, 12 Oct 2009 10:55:46 +0200
>
> > And David we still have this sparc bug open, which I forwared to
> > grub-devel:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538030
>
> I'm about to head to Tokyo for the Linux Kernel summit and
> the Japan Linux Symposium so I'll be out of commission for
> a few weeks again.
>
> Right when I'm about to get back to even trying out the latest
> GRUB I hit another conference or major trip.
>
> So please do not make me the critical link in the chain for Sparc
> things until later this year. If these things are to be fixed sooner
> than that, someone else will need to look into them.
Thanks for looking into this, even if it's not now :)
Unfortunately AFAIR you're the only sparc guy on the list here or am I
wrong?
For me this isn't that important. For the 1.97 release I wouldn't anyway
declare sparc as a fully stable port.
And in Debian powerpc and sparc isn't that much used.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
next prev parent reply other threads:[~2009-10-12 9:42 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 8:55 powerpc/sparc problems Felix Zielcke
2009-10-12 9:05 ` David Miller
2009-10-12 9:42 ` Felix Zielcke [this message]
2009-10-12 9:56 ` Vladimir 'phcoder' Serbinenko
2009-10-12 10:11 ` David Miller
2009-10-12 10:27 ` Felix Zielcke
2009-10-12 9:26 ` Vladimir 'phcoder' Serbinenko
2009-10-12 9:33 ` Felix Zielcke
2009-10-20 18:07 ` rubisher
2009-10-20 20:24 ` Vladimir 'phcoder' Serbinenko
2009-10-21 15:59 ` rubisher
2009-10-12 9:58 ` Bean
2009-10-12 10:14 ` David Miller
2009-10-12 10:26 ` Vladimir 'phcoder' Serbinenko
2009-10-12 10:28 ` David Miller
2009-10-12 15:29 ` Pavel Roskin
2009-10-12 15:45 ` Vladimir 'phcoder' Serbinenko
2009-10-12 22:03 ` Pavel Roskin
2009-10-12 23:39 ` David Miller
2009-10-15 11:58 ` Vladimir 'phcoder' Serbinenko
2009-10-15 22:41 ` Pavel Roskin
2009-10-16 12:44 ` David Miller
2009-10-16 14:10 ` Pavel Roskin
2009-10-17 1:21 ` Pavel Roskin
2009-10-17 9:08 ` Vladimir 'phcoder' Serbinenko
2009-10-17 10:11 ` Robert Millan
2009-10-20 21:38 ` [PATCH] auto-generate libgcc.h Robert Millan
2009-10-21 6:28 ` Vladimir 'phcoder' Serbinenko
2009-10-21 15:55 ` rubisher
2009-10-21 21:00 ` Vladimir 'phcoder' Serbinenko
2009-10-23 16:19 ` rubisher
2009-10-12 10:31 ` powerpc/sparc problems Bean
2009-10-12 11:07 ` David Miller
2009-10-12 14:05 ` Bean
2009-10-14 16:37 ` Robert Millan
2009-10-21 16:03 ` rubisher
2009-10-21 20:15 ` Bean
2009-10-28 10:24 ` Felix Zielcke
2009-10-28 10:29 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2009-10-22 9:12 rubisher
2009-10-22 9:31 ` Bean
2009-10-23 20:34 ` rubisher
2009-10-24 6:13 ` Bean
2009-10-25 15:22 ` rubisher
2009-10-25 15:57 ` Bean
2009-10-26 21:06 ` rubisher
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=1255340545.3204.33.camel@fz.local \
--to=fzielcke@z-51.de \
--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.