How to resolve hiccups by patch program?

[SF Markus Elfring]

> I have yet to see a patch reject that was created by patch(1) without good reason.

Do you know a kind of debug version for the patch program that provides verbose explanations?
Are there any chances to get more informations about the reason?


> There are sure to be conflicts of some sort in the patch.

Can you see it from the example reject file "app_db.c.rej" in the referenced issue tracking system?
http://bugs.digium.com/file_download.php?file_id=12652&type=bug
(I'm sorry - I recognise only my intended updates.)


> If there are any conflicts at all, they need to be resolved by human
> intervention -- there is no other way to be sure that the patch may be
> applied without producing an incorrect result.

This intervention depends on the willingness for cooperation of the involved software developers. (It seems that I get on the nerves of the other side because of their expectations with bug reporting and coding guidelines.)

Regards,
Markus