Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!ginosko!usc!ucsd!nosc!trout.nosc.mil!broman From: broman@schroeder.nosc.mil (Vincent Broman) Newsgroups: comp.os.minix Subject: Re: Important new program: cleanit.c Message-ID: Date: 5 Oct 89 15:36:03 GMT References: <3492@ast.cs.vu.nl> Sender: nobody@nosc.NOSC.MIL Reply-To: broman@nosc.mil Organization: Naval Ocean Systems Center, San Diego Lines: 22 In-reply-to: ast@cs.vu.nl's message of 4 Oct 89 21:39:17 GMT > What do people think of the suggestion of defining a posting standard > in which everything before the cut line is junk and can be discarded? Not very useful. There is already a standard way to separate posting headers from the text of the message: they are separated by the first blank line in the article. "Cut here" lines do not separate junk from good stuff, they separate the contents of a file from non-contents of that file, giving it a well-defined boundary. If AST is going to be posting stuff in uuencoded form, notice that uudecode already ignores things before "begin" and after "end", if there is only one uuencoded piece in the article. I would suggest this: 1. create humungous compressed tar or shar file, 2. split it into small binary chunks, 3. uuencode each chunk and post it individually. It's too bad that floppy-only systems seem to be excluded from any of this action, because the big compressed archive probably won't fit on a floppy. Vincent Broman, code 632, Naval Ocean Systems Center, San Diego, CA 92152, USA Phone: +1 619 553 1641 Internet: broman@nosc.mil Uucp: sdcsvax!nosc!broman