context: Generally it's best to post the patches on the SourceForge project page, to make sure they don't get lost.
answer_0: Inevitably, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_1: Thereafter, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_2: Often, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_3: Currently, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_4: Presently, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_5: In turn, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_6: Nationally, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_7: Immediately, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_8: Also, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."
answer_9: Now, "Please use the unified diff (`` diff -u""or``cvs diff -u"") when generating patches; they're easier to read and apply more easily."