On Tue, 22 Aug 2000, I Lee Hetherington wrote:
> Perhaps so that diff/patch will work and people can pass around ascii
> patch files?
True.
> There are currently no binary files inside a kernel
> tarball.
Wrong.
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.
True.
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 majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 23 2000 - 21:00:07 EST