Linus Torvalds says Linux kernel will remain GPL v2
dylanmccall at gmail.com
Sat Jan 19 04:57:04 GMT 2008
Well, you'll never see me posting shortened URLs.
...or following the RFC, for that matter. In my opinion, the job of making
long lines look nice should be handled by the viewer (the mail program in
this case) and only the viewer. Data should not be mangled for the sake of
human readability, because it is good for way more than just direct human
consumption. (As any good search engine can tell us -- Google Books Search
is a neat example, where it finds popular passages and says where they have
That is also my philosophy with code, which may explain why I can never seem
to create tidy patches :P
Still, I think it is an intuitive way to go, and would make sense if there
were text editors making such code look "normal" to the crazy
space-indenters out there.
On Jan 18, 2008 7:47 PM, Michael R. Head <burner at suppressingfire.org> wrote:
> On Fri, 2008-01-18 at 18:57 +0100, Mario Vukelic wrote:
> > On Fri, 2008-01-18 at 14:55 +0100, Jan Claeys wrote:
> > >
> > > I see no good reason to fold URLs?
> > RFC 2822 is a good enough reason ;)
> > 2.1.1. Line Length Limits
> > There are two limits that this standard places on the number of
> > characters in a line. Each line of characters MUST be no more than
> > 998 characters, and SHOULD be no more than 78 characters, excluding
> > the CRLF.
> > http://www.rfc-editor.org/rfc/rfc2822.txt
> So, according to the RFC, posting a long URL (as long as it's less than
> 998 characters in length) is OK.
> Go forth and unfold your URLs!
> Michael R. Head <burner at suppressingfire.org>
> sounder mailing list
> sounder at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sounder