Re: Binary files in the kernel sources?

From: Brian Gerst (bgerst@didntduck.org)
Date: Tue Aug 22 2000 - 12:50:16 EST

Next message: kuznet@ms2.inr.ac.ru: "Re: dev_mc_lock question."
Previous message: Jens Axboe: "Re: Ramdisk / sync deadlock"
In reply to: Matthias Andree: "Re: Binary files in the kernel sources?"
Next in thread: Matthias Andree: "Re: Binary files in the kernel sources?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Matthias Andree wrote:
>
> > > Uh. uuencode? History. base64encode COULD be used, but what's the point
> > > as long as it's inside a .tar.ANYCOMPRESSORSUFFIX?
> >
> > Excuse me? I've never heard of that program.
> >
> > The only alternative to uuencode would be a png-logo.c or
> > png-logo.pl that spits out a png file without external help.
>
> 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.

Brian Gerst - 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/

Next message: kuznet@ms2.inr.ac.ru: "Re: dev_mc_lock question."
Previous message: Jens Axboe: "Re: Ramdisk / sync deadlock"
In reply to: Matthias Andree: "Re: Binary files in the kernel sources?"
Next in thread: Matthias Andree: "Re: Binary files in the kernel sources?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Aug 23 2000 - 21:00:07 EST