From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Kernel support for VESA Bios Extension
Date: Fri, 15 Jul 2005 12:53:33 +0200 [thread overview]
Message-ID: <200507151253.33360.okuji@enbug.org> (raw)
In-Reply-To: <87hdex5af3.fsf@student.han.nl>
On Thursday 14 July 2005 23:45, Marco Gerards wrote:
> I personally prefer not using that many `*'s and believe it is not in
> the GCS. But I think Okuji uses this as well, but I don't. Perhaps
> we need our own guidelines for such things, I think consistency is
> important. Okuji, what you you think?
I don't need strict rules here. As far as I see, GNU does not define anything
about this.
But I myself don't use aterisks except for the license term in C, do I?
Okuji
next prev parent reply other threads:[~2005-07-15 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 18:36 [PATCH] Kernel support for VESA Bios Extension Vesa Jääskeläinen
2005-07-14 19:02 ` Marco Gerards
2005-07-14 20:36 ` Vesa Jääskeläinen
2005-07-14 21:45 ` Marco Gerards
2005-07-15 10:53 ` Yoshinori K. Okuji [this message]
2005-07-15 16:47 ` Vesa Jääskeläinen
2005-07-15 18:55 ` Yoshinori K. Okuji
2005-07-16 18:43 ` 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=200507151253.33360.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.