All of 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: status update for grub 2 developments?
Date: Mon, 18 Jun 2007 15:32:04 +0200	[thread overview]
Message-ID: <20070618133204.GA30651@aragorn> (raw)
In-Reply-To: <46765CF7.7040107@gmail.com>

On Mon, Jun 18, 2007 at 12:22:47PM +0200, adrian15 wrote:
>     * pause command

How about calling it "read" command, and giving it read-like syntax, to keep
the trend of maintaining some consistency with the GNU cli environment?

> # Short term development
>     * grub-disk scripts

Not sure what you mean with grub-disk scripts.  Do you mean scripts to
generate rescue disks?  If so, then this is already implemented.  Look
at grub-mkrescue in CVS.

(but of course, there's room for improving it)

> >Ideas are welcome where to store this information are also welcome :).
> >We would need to track requirements for features on component level.
> >More automated the better.
> 
> Can we use the bugs system maybe?
> A friend of mine uses trac ( http://trac.edgewall.org/ ) and he likes it 
> a lot. I do not know if it fits our needs.

We have a bug system in Savannah, but it's occupied by GRUB Legacy.  I guess
this is why we're not using it?

Oh btw, are we going to ditch GRUB Legacy anytime soon? :-P

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.



  reply	other threads:[~2007-06-18 13:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17 12:47 status update for grub 2 developments? Vesa Jääskeläinen
2007-06-17 13:34 ` Robert Millan
2007-06-18  2:52 ` Ashok kumar
2007-06-18 10:22 ` adrian15
2007-06-18 13:32   ` Robert Millan [this message]
2007-06-18 15:40     ` Vesa Jääskeläinen
2007-06-19 12:13       ` adrian15
2007-06-19 15:13         ` Vesa Jääskeläinen
2007-06-19 12:08     ` adrian15
2007-06-23 12:57 ` Marco Gerards
2007-06-23 14:31   ` Bean
2007-06-23 14:50     ` Marco Gerards
2007-06-24  4:22       ` Bean
2007-06-24 11:47         ` Bean
2007-07-22 12:42           ` Marco Gerards
2007-06-23 14:52     ` Marco Gerards
2007-06-23 15:59       ` Bean
2007-06-23 16:10         ` Marco Gerards
2007-06-23 16:23           ` Bean
2007-06-23 16:38             ` Marco Gerards
2007-06-23 20:19               ` Yoshinori K. Okuji
2007-07-01 17:49     ` adrian15
2007-06-25 18:41       ` Bean
2007-06-26  4:13   ` Ashok kumar
2007-07-22 14:31     ` 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=20070618133204.GA30651@aragorn \
    --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.