If this was something I wanted to get merged into the release code, then I might do a diff format, but as it is, I believe the current race limitation in the code is intentional.
With that being the case, and since the code can change considerably between releases, I feel that a diff setup would only be useful when the source file that a server-op wants to modify is from the same revision as the one used when the diff was generated. I have no interest or intention of maintaining a diff over multiple revisions. As such, I believe that it is better, in the long run, to leave my instructions as they are. I also don't believe that my instructions are particularly difficult to understand, at least not for someone with a good grasp of the English language and a basic grasp of C++ programming. It may be less convenient for some, especially if they don't want to read much, but if followed from start to finish without trying to skim or skip anything, it should be perfectly understandable and easy to follow.
But, if you really want to have it presented in diff format, feel free to do it yourself. I have no problem with that at all.
Later,
Drake Phoenix
|