[lkml]   [1999]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] kernel API documentation system
On Sun, Sep 26, 1999 at 06:48:16PM +0100, Alan Cox wrote:
> > I can understand using an encoding scheme for graphics, but I'm really not
> > thrilled about using an encoding for text. Neither is Linus, by the way.
> For patches it is very useful. I get a fair number of mailers that
> seem to like to trash patch files, but none that eat mime encoded
> attachments.

Sure, that's fine, but as others have pointed out mime isn't the end all
to be all. And I thought the discussion was about text stuff, not patches.

For patches, you'll be happy to know that BitKeeper supports wrapping and
unwrapping when you use email as your transport. The following will wrap
the latest changes and apply them someplace else:

$ bk send -wuu

On the other end

$ cat mailmessage | bk receive ~/kernel # this autounwraps

The wrapping code is as follows and people are welcome to it:


# uuwrap - the sending side of a uuencode stream
exec uuencode bkpatch$$


# unuuwrap - the receiving side of a uuencode stream

cd /tmp
cat > $TMP
uudecode $TMP
set `grep '^begin ' $TMP`
if [ ! -r $FILE ]
then chmod 0664 $FILE
cat $FILE
/bin/rm -f $FILE $TMP
exit 0
Larry McVoy

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 13:54    [W:0.051 / U:0.732 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site