"James Montgomerie" wrote:
>
> "Martin Sevior" wrote:
> >
> > On Wed, 5 Apr 2000, Tomas Frydrych wrote:
> >
> >
> > Generally one sends a patch against the current source tree to
> > [EMAIL PROTECTED] AND to [EMAIL PROTECTED]
> >
> > I've found the best way to generate patches is to use the command
> >
> > diff -Naur --exclude="CVS" --exclude="Linux*" abi new-abi >
> > my_new_feature.patch
> >
> > where "abi" is the current abi source tree and "new_abi" is your
new
> > source tree with your new feature added.
> >
>
> It suggests to me that 'cding' to the abi directory you've been
working
> in then doing a 'cvs -diff -N' will generate a diff file for the
entire
> tree, including and removed of added files. This eliminates the
need
> for a spare 'clean' copy of the source tree (you might want to have
one
> for reference though).
>
> You might want to try a 'cvs -diff -N -c 3 -p' for more readable
patches
> (is there an AbiSource policy on a prefered diff format?)
Just thought - watch out that doesn't include things like your compiled
binaries (excluded explicitly in Martin's manual diff). It is, however,
intelligent enough not to include CVS directories :-)
cvs diff --help gives cvs' diff options.
Jamie.
