Do try to somehow show where your hacks are.
For example, avoid adjusting comments and variable names and formatting in
code that you are not otherwise changing
so it is easy to run a unix diff on the two files. ??Better yet, use lots
of #ifdef's and comments to make it obvious to the casual reader.
Jerry, KE7ER
Reformatting makes it easier to read.
diff -b ignore changes in white space.
But I don't plan on messing with the Raduino code. I'm in the process of
writing one myself.
Vince - KA8CSH
--
Michigan VHF Corp.
