As mentioned in the color codes thread, I'm in the process of merging an antique MUD codebase (originally Circle 3.0 bpl5, merged in stages up to bpl8 and then 3.1, but there's even some stuff that was originally written for a Diku Gamma MUD back in 1992 or so) up to 3.61.
One of the fortuitous side-effects of this is that a sizeable percentage of the 3.61 code gets an eyes-on code review and there's lots of tiny (and a few larger) things turning up.
What's your preferred route for receiving the candidate fixes? I think the best route that's easy for me would be to make the changes to 3.61, with notes of the rationale behind each, and email you a zip of src/ - you can then apply a three-way merge if things have changed substantially in the TOT. I could in theory work with the repository myself, but I use Mercurial at home and P4 at work and would prefer not to have to muddy my tiny brain with a third SCM unless I really have to :) .
However, that gives you everything in one batch and that might not be what you want; a simple enhancement to the process would be to split out any changes with nonlocal effects into separate zips, perhaps?
An alternative would be to generate the diffs for each individual change from Mercurial, if you want finer-grained changes? The Mercurial patch format is similar (but, as far as I'm aware, not identical) to diff output.
Or I could simply supply the text file describing each suggested change in detail.
Let me know what you think.
Cheers
Dave





