🚀 go-pugleaf

heitkoet@lusty.informatik.uni-dortmund.de (Joerg Heitkoetter) writes:

> Submitted-by: joke@ls11.informatik.uni-dortmund.de
> Archive-name: b2c-0.99j/part01
>
> ---- Cut Here and feed the following to sh ----
> #!/bin/sh
> # This is b2c-0.99j, a shell archive (produced by shar 3.49)
> # To extract the files from this archive, save it to a file, remove
> # everything above the "!/bin/sh" line above, and type "sh file_name".
> #
> # made 12/18/1992 18:19 UTC by joke@ls11.informatik.uni-dortmund.de
> # Source directory /tmp_mnt/home/ls11a/heitkoet/magpie/b2c
> #
> # existing files will NOT be overwritten unless -c is specified
> #
> # This shar contains:
> # length  mode       name
> # ------ ---------- ------------------------------------------
> #   1614 -rw-r----- Makefile
> #    811 -rw-r----- MAGPIE
> #  17982 -rw-r----- LICENSE       <------
> #    405 -rw-r----- README        <------

I know this has been said before, but allow me to say it yet again.
Please, please, PLEASE... if you must include the GNU License in your
source posting, at _least_ put the README at the beginning of the shar!
I really dislike having to page through 20K of text just to find out
what the hell a source posting is.  A descriptive introduction or a
'Part 0/4' article is even better.

I have nothing against GNU, nor do I object to the License being
included with the sources (unless it's larger than the sources).  But
can't you stick it at the end of the shar?  Trust me, I don't need to
read it again.

Thank you for your support, and now, back to your regularly scheduled
mayhem.  Observe followups.
--
Roy M. Silvernail --  roy%cybrspc@cs.umn.edu - OR-  cybrspc!roy@cs.umn.edu
   "I like Santa Claus as well as the next guy, but do you really want a
   hard drive that's spent 6000 miles at the bottom of a canvas sack in a
            wooden sleigh powered by airborne reindeer?" -- me