This is the mail archive of the patchutils-list@sourceware.org mailing list for the patchutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: How to resolve hiccups by patch program?


On Thu, 2007-01-04 at 09:04 +0100, SF Markus Elfring wrote:
> 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.)

Need to see the file it's being applied to.  Commonly a reject will be
because the file the patch was made against is not the same as the file
the patch is applied to.

> 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.)

No -- you just need to create a clean patch in the first place, i.e. one
that applies directly to the same file the developer is using. :-)

It sounds like the tool you're using is generating the patch against a
different revision that you intend.

Tim.
*/

Attachment: signature.asc
Description: This is a digitally signed message part


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]