From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: status update for grub 2 developments?
Date: Sat, 23 Jun 2007 16:50:56 +0200 [thread overview]
Message-ID: <87645eohbj.fsf@xs4all.nl> (raw)
In-Reply-To: <20070623143127.GA2433@ws3.vdp.com> (bean123@126.com's message of "Sat, 23 Jun 2007 22:31:27 +0800")
Bean <bean123@126.com> writes:
> On Sat, Jun 23, 2007 at 02:57:30PM +0200, Marco Gerards wrote:
>> Something I think is important for GRUB 2 is regression testing. So
>> we can make sure things like scripting works, filesystems work
>> correctly, etc.
>
> I can't agree more. I think major bug should be fixed as soon as possible,
> otherwise grub2 wouldn't be that useful.
>
>> Well, if people want to work on scripting or networking they should
>> talk to me. I have lots of code on my hd that is incomplete or just
>> not cleaned up. It would be a waste of time if it were rewritten.
>> And please poke me a lot to get me to work... ;)
>
> I'm interested in scripting. What could I do to help you ?
For example, you could implement the expr command. For that you
need to write a simple expression parser. It should just be like you
use on the console (see "man expr"). You could even use bison, or
write a recursive descent parser.
Another thing you can do is going over my code. Check if it is sane,
makes sense, etc. I am the first person to admit that I am no parser
expert. There was just no one else doing this the way I wanted, so I
just picked up this task.
So you could figure out how things work, figure out if things can be
improved or cleaned up (especially the memory handling and lexer).
This is a hard task because you have to understand the code. But it
leaves you in a position to fix bugs and improve the design and even
extend it!
Feel free to ask lots of questions. I rather tell you on beforehand
how things should be done, instead of telling your patches are wrong.
IRC can, for example, be a good way to discuss some things like these.
--
Marco
next prev parent reply other threads:[~2007-06-23 14:50 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
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 [this message]
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=87645eohbj.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.