This directory contains an automatic patch generator.  You must have RCS
to use this.  You must also have run packinit in the top level directory
of your package to create a .package file.

When you've modified a file in your package, the pat program is used to
control the whole process.  The other programs can be called by hand, but
usually needn't be.  Run pat from the top level directory of your package.

There is also program called mailagent that will read your incoming mail and
mail patches to people automatically.  You'll have to customize mailpatch
for yourself.

The pat, patcil, patdiff, and patbase programs take a list of filenames as
arguments.  Alternately, a -a means all files listed in MANIFEST.new.

Patcil will create an RCS directory if necessary.  However, it may not check in
things which require special initializaton properly.  For example, if you
want to check in a shell script, you'd better make your RCS directory yourself
and then say

	rcs -i -c'# ' blurfl.xsh

before running pat or patcil.  Otherwise the RCS log may not be commented
properly.

Patdiff will create a bugs directory in your top level directory, and will want
to find a patchlevel.h file in that same directory.  Everything is done from
that top level directory--don't put any patchlevel.h or bugs directories in
your subdirectories.  Each subdirectory has its own RCS directory though.

Patpost, patsend and patftp may be used to post to Usenet, mail to someone,
or copy patches to your ftp directory.  They take a destination and a list
of patches to process.
