Your mkcvspatch script is pretty sophisticated. It does some things
that genpatch does not. Maybe what would be ideal would be a script
that generates the patch, like genpatch, and another than verifies the
build tree and or resulting patch, like mkcvspatch. The latter could be
used server side by the cvs comitter.
In any case since genpatch "didn't cause very much excitement" either
I'm assuming that each developer has their own way of generating patches
that they are comfortable with.
Patrik Stridvall wrote:
>
> > 2. It'd be nice to be able to only diff the things I really want to
> > submit (i.e. specify arguments to cvs diff).
>
> Well, I posted script called mkcvspatch to the list almost a year ago.
> It didn't cause very much excitement, so I didn't bother posting
> any new versions.
>
> I use this script for every patch I send in, it can do the following.
>
> 1. Checks that all specified files exists and are modified or new.
> 2. Checks that all modified files are specified.
> 3. Checks that all new files in existing directories are specified.
> 4. Can divide the changes in to several patches.
> 5. Puts existing files as diffs and new files as tars.
>
> It only works with a online connection to the CVS.
> It could be adapted to work without it but I have
> nether bothered doing so.
>
> ---8<---
>
> Example of <specfile>:
> *** patch1
>
> * dir1/file1.c,
> dir2/file2.c:
> Reason for modification of dir1/file1.c and dir2/file2.c.
>
> * dir1/file3.c:
> Reason for modification of dir1/file3.c.
>
> *** patch2
>
> * dir3/file4.c:
> Reason for modification of dir3/file4.c.
>
> This file generates the files patch1.diff and patch2.diff and if there
> are any new files in either patch also patch1.tar and/or patch2.tar.
>
> ---8<---
>
> ------------------------------------------------------------------------
> Name: mkcvspatch
> mkcvspatch Type: unspecified type (application/octet-stream)
> Encoding: quoted-printable
--
Steven Elliott ([EMAIL PROTECTED])
