From: Randy Dunlap <rdunlap@xenotime.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Simon Horman" <horms@verge.net.au>,
"liu weni" <qingshenlwy@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Toralf Förster" <toralf.foerster@gmx.de>
Subject: Re: [PATCH v2]kernel: remove mess codes
Date: Sun, 13 Dec 2009 17:19:44 -0800 [thread overview]
Message-ID: <20091213171944.a1ef2af0.rdunlap@xenotime.net> (raw)
In-Reply-To: <4B258A27.3050006@goop.org>
On Sun, 13 Dec 2009 16:43:19 -0800 Jeremy Fitzhardinge wrote:
> On 12/13/09 16:33, Simon Horman wrote:
> > On Sat, Dec 12, 2009 at 11:04:48PM -0800, Jeremy Fitzhardinge wrote:
> >
> >> On 12/12/09 22:55, liu weni wrote:
> >>
> >>> I found some mess characters(0x0c) in the kernel source code.
> >>> Then I suggest remove it.
> >>>
> >> Those are form-feed characters. Some editors use them to separate
> >> logically distinct blocks of code into separate "pages".
> >>
> > I can see their value in documentation, but I struggle to imagine
> > their usefulness in code.
> >
>
> I think a folding editor can fold them out, so you can just expand the
> area you're interested in. Or something. The point is that it is
> formatting that was presumably put there by the original author. Unless
> they're actually upsetting something, I'd be inclined to leave them.
and if someone prints them on paper, the form-feed character will cause
a, uh, form feed (new page).
---
~Randy
next prev parent reply other threads:[~2009-12-14 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 6:55 liu weni
2009-12-13 7:04 ` Jeremy Fitzhardinge
2009-12-14 0:33 ` Simon Horman
2009-12-14 0:43 ` Jeremy Fitzhardinge
2009-12-14 1:16 ` Simon Horman
2009-12-14 1:19 ` Randy Dunlap [this message]
2009-12-13 13:58 ` Pavel Machek
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=20091213171944.a1ef2af0.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=horms@verge.net.au \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qingshenlwy@gmail.com \
--cc=toralf.foerster@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®