lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sun, 13 Dec 2009 17:19:44 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Simon Horman <horms@...ge.net.au>,
	liu weni <qingshenlwy@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Toralf Förster 
	<toralf.foerster@....de>
Subject: Re: [PATCH v2]kernel: remove mess codes

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ