From: Pavel Roskin <proski@gnu.org>
To: grub-devel@gnu.org
Subject: Proposal for GNU indent compatibility
Date: Fri, 19 Jun 2009 12:37:20 -0400 [thread overview]
Message-ID: <1245429440.28417.29.camel@mj> (raw)
Hello!
In order to encourage developers to use proper indentation on the newly
added code, I suggest that we accept the default style of GNU indent.
That is, the space after "!" should not be needed. That's the only
difference I'm aware of.
Running indent on the code and then adding spaces after "!" is
ridiculous, in my opinion. GRUB and indent are both GNU programs, it
should not be needed to do such things.
That doesn't mean that we should start reformatting the existing code.
Neither does it mean that it's acceptable to submit code that GNU indent
failed to format nicely.
--
Regards,
Pavel Roskin
next reply other threads:[~2009-06-19 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 16:37 Pavel Roskin [this message]
2009-06-19 17:01 ` Proposal for GNU indent compatibility Vladimir 'phcoder' Serbinenko
2009-06-19 21:52 ` Pavel Roskin
2009-06-21 11:25 ` Robert Millan
2009-06-21 11:41 ` Alfred M. Szmidt
2009-07-31 8:03 ` 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=1245429440.28417.29.camel@mj \
--to=proski@gnu.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.