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: Google Summer of Code 2007
Date: Wed, 14 Mar 2007 12:14:22 +0100	[thread overview]
Message-ID: <87veh46prl.fsf@xs4all.nl> (raw)
In-Reply-To: <7e62748d0703131852s595befe2u97bed118d5786dc8@mail.gmail.com> (Brandon Sho's message of "Wed, 14 Mar 2007 10:52:52 +0900")

"Brandon Sho" <borochan@gmail.com> writes:

> I agree wholeheartily with Jeroen's last paragraph below.
>
> Some might even add that this should have been done sooner

That means you will send in patches?
 .
> As an observer I have not noticed any remarkable gain or needed
> functionality added for quite some time.   Its been years and you
> still don't have a production version..   And you should at least
> attempt for the legacy features as a proof of stability and then later
> you can add features as it matures.

That is what we have been doing for quite a while.  Our main focus was
working towards a release and if you look carefully you will see there
was quite some progress over these years, although GRUB is the kind of
project in which you do not immediately notice features, like in a
project with a fancy GUI.  I mean: the user will not see when for
example a filesystem is supported, but the user will see when it is
not supported.

I hope you understand all of us are volunteers.  Sometimes we do not
have time to work on GRUB, in that case simply nothing happens.
Sometimes we think it is fun to add a feature, even if it isn't
required for the release.  But you can't blame anyone for that, if we
don't accept patches like these, people will start working on other
fun projects.  I think most of us know perfectly well what to do in
order to get GRUB 2 stable and to replace GRUB Legacy and we are all
working on this as a top priority.

--
Marco




  reply	other threads:[~2007-03-14 11:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 17:17 Google Summer of Code 2007 Yoshinori K. Okuji
2007-03-06 10:44 ` Johan Rydberg
2007-03-06 17:07   ` Thomas Schwinge
2007-03-06 17:56     ` Er Zapito
2007-03-06 21:49     ` Jeroen Dekkers
2007-03-10 21:38       ` Jeroen Dekkers
2007-03-12 17:45         ` Yoshinori K. Okuji
2007-03-13 12:38           ` Jeroen Dekkers
2007-03-13 16:44             ` Yoshinori K. Okuji
2007-03-13 17:36               ` Marco Gerards
2007-03-13 22:39                 ` Thomas Schwinge
2007-03-15 10:26               ` Jeroen Dekkers
2007-03-21  4:02                 ` Yoshinori K. Okuji
2007-03-14  1:52             ` Brandon Sho
2007-03-14 11:14               ` Marco Gerards [this message]
2007-03-19  4:38                 ` Brandon Sho
2007-03-07 13:45 ` Marco Gerards
     [not found] <200703151705.l2FH53LC032672@correoredir01.dinaserver.com>
2007-03-19  8:11 ` adrian15
  -- strict thread matches above, loose matches on Subject: below --
2007-02-25  7:59 Shawn O. Pearce
2007-02-27 20:47 ` Johannes Schindelin
2007-02-28  8:42 ` Andy Parkins
2007-02-28  9:03   ` Matthieu Moy
2007-03-02 20:36     ` Johannes Schindelin
2007-02-28  9:35 ` Raimund Bauer
2007-02-28 15:39   ` Brian Gernhardt
2007-02-28 15:47     ` Shawn O. Pearce
2007-02-28 16:00       ` Brian Gernhardt
2007-03-01  2:08 ` Jakub Narebski
2007-03-01  8:03   ` Matthieu Moy
2007-03-01 21:34   ` Shawn O. Pearce
2007-03-04 22:10     ` Martin Langhoff

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=87veh46prl.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.