On 20-Jun-98 Greg A. Woods spoke unto us all:
# What I was talking about was creating the patches in the first place.
# There are no tools in existance that create patch sets that follow the
# guidelines (i.e. one "change" per file, etc.).  This could be done with
# CVS, but it would still be *VERY* tedious.  Actually using CVS to try
# and manage a pkgsrc module isn't much gain at all.

This is wholly off topic.. but since you brought it up.. (and because it may
benefit others attempting to do this)

I use a collection of scripts I wrote to do this:  very simple quick hacks.

Two are available at my web page www.futureone.com/~garbled
One breaks a massive diff into lots of little diffs (useful for fixing freebsd
style diffs)

The other one quickly replaces ifdef __FreeBSD__ with both freebsd and netbsd
defs. It is meant to be run on patches.

This quick script, creates diffs by searching the tree for .orig files.  I use
it with an alias called orig, which creates an original and loads the .c file
into an editor.

Again.. very simplistic.. but they save me hours of work.

#!/usr/pkg/bin/perl

if ($ARGV[0]) {
        $begin = $ARGV[0];
} else {
        $begin = "aa";
}
$new = 0;

@files = `find . -name \\\*.orig -print`;

foreach $orig (@files) {
  chomp($orig);
  $orig =~ s+^\./++;
  $new = $orig;
  $new =~ s/.orig//;
  system("diff -U 1 $orig $new >../patch-$begin");
  $begin++;
}


---
Tim Rightnour    -  root@garbled.net
http://www.zynetwc.com/~garbled/garbled.html