[lkml]   [2000]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Binary files in the kernel sources?
On Tue, 22 Aug 2000, I Lee Hetherington wrote:

> Perhaps so that diff/patch will work and people can pass around ascii
> patch files?


> There are currently no binary files inside a kernel
> tarball.


On Tue, 22 Aug 2000, Brian Gerst wrote:

> Matthias Andree wrote:
> > I'm asking again: what's the point in encoding binary files such as PNG,
> > if the whole lot is stuffed into a .tar.gz or .tar.bz2 anyways?
> Diff and patch can't handle binary files.


Still, for uuencoding, there are far too many implementations of
uuencode around (with/out checksum, with/out boundary, using blanks
(0x20) or backticks (0x60)), and finally, uuencode is trashed when
quoted-printable encoded.

These considerations are overcome by MIME which is well-defined. Wrong
implementations of a well-defined standard may not be excused, flaky
implementations of a not-so-well "standard" are to be avoided.

Note that particularly, 8 years after RFC 1521/1522 (which have not
really changed in 2045..2049), there is absolutely no excuse for a lack
of MIME support.

Matthias Andree
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:37    [W:0.089 / U:2.684 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site