> 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.
Well, as I said, I could easily add a flag (say -g) to mkcvspatch that
automatically generated a patch file.
However ...
> 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.
... since as you say neither my mkcvspatch nor your genpatch caused
much excitement I simple haven't bothered.
I might do it anyway since it would be at least of some use to me,
but don't hold your breath, writing a patch description file manually
is very easy.
You (or somebody else) are welcome to send me a patch though. :-)
