From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Kernel support for VESA Bios Extension
Date: Sat, 16 Jul 2005 20:43:00 +0200 [thread overview]
Message-ID: <87zmsmegnf.fsf@student.han.nl> (raw)
In-Reply-To: <200507152055.05319.okuji@enbug.org> (Yoshinori K. Okuji's message of "Fri, 15 Jul 2005 20:55:05 +0200")
"Yoshinori K. Okuji" <okuji@enbug.org> writes:
> On Friday 15 July 2005 18:47, Vesa Jääskeläinen wrote:
>> > After the comment add a `.' and two spaces instead of one. This is
>> > true for all comments.
>>
>> Odd... Especially that two spaces. But I don't want to start another
>> "war" with this ;)... So I try to adapt.
>
> According to the GNU Coding Standards, two spaces are useful for Emacs to
> identify the end of a text. I myself do not see any problem without two
> spaces in Emacs, so I agree that it looks strange. But... this is what the
> GNU Coding Standards says, and I have no problem with this rule, so we follow
> it.
I do remember having some problems in emacs if this is not used. But
I don't remember what the exact problems are. To avoid further
problems and because of the GCS I really prefer two spaces in both
comments and changelog entries.
--
Marco
prev parent reply other threads:[~2005-07-16 18:54 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
2005-07-15 16:47 ` Vesa Jääskeläinen
2005-07-15 18:55 ` Yoshinori K. Okuji
2005-07-16 18:43 ` Marco Gerards [this message]
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=87zmsmegnf.fsf@student.han.nl \
--to=metgerards@student.han.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.