From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] use at_keyboard.c on i386-ieee1275
Date: Thu, 24 Jan 2008 09:40:31 +0100 [thread overview]
Message-ID: <200801240940.31521.okuji@enbug.org> (raw)
In-Reply-To: <87fxword4x.fsf@xs4all.nl>
On Wednesday 23 January 2008 12:32, Marco Gerards wrote:
> > Which reminds me, is 1.96 coming soon? When lvm/raid, reiserfs and
> > powerpc issues are fixed, it might be a good time. What do you think?
>
> Fine for me, we didn't have a release for quite a while. To be
> honest, I just hate the upload procedure of ftp://alpha.gnu.org. The
> documents can be interpreted in two ways, or my English simply sucks.
> That's one reason for me not to release that quickly. ;-)
Just leave the task to me. I have been the release manager for long, thus I
know how to do it right.
All I need is ping from Robert. My preference is to publish a new version
regularly, no matter whatever bugs remain (yeah, I am very aggressive in GRUB
2), but he stopped me releasing 1.96 previosly, IIRC.
Okuji
next prev parent reply other threads:[~2008-01-24 8:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 10:47 [PATCH] use at_keyboard.c on i386-ieee1275 Robert Millan
2008-01-23 10:58 ` Marco Gerards
2008-01-23 11:18 ` Robert Millan
2008-01-23 11:32 ` Marco Gerards
2008-01-23 11:56 ` Robert Millan
2008-01-24 8:40 ` Yoshinori K. Okuji [this message]
2008-01-24 9:10 ` Marco Gerards
2008-01-24 12:39 ` Robert Millan
2008-01-24 12:56 ` Marco Gerards
2008-01-24 21:26 ` Yoshinori K. Okuji
2008-01-24 21:55 ` Robert Millan
2008-01-25 8:56 ` Marco Gerards
2008-01-25 21:22 ` Yoshinori K. Okuji
2008-01-25 22:57 ` next release & NEWS file (Re: [PATCH] use at_keyboard.c on i386-ieee1275) Robert Millan
2008-01-27 8:01 ` Pavel Roskin
2008-01-27 22:03 ` Robert Millan
2008-01-28 8:53 ` [PATCH] use at_keyboard.c on i386-ieee1275 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=200801240940.31521.okuji@enbug.org \
--to=okuji@enbug.org \
--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.