From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Tim Waugh <twaugh@redhat.com>
Cc: patchutils-list@sourceware.org
Subject: Re: How to resolve hiccups by patch program?
Date: Fri, 05 Jan 2007 10:26:00 -0000 [thread overview]
Message-ID: <1387612361@web.de> (raw)
> 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. :-)
Would you like to try a comparison with the current development revision to check if my update suggestion (context-diff from "app_db.c.rej") is still valid?
http://svn.digium.com/view/asterisk/trunk/apps/app_db.c?rev=47783&view=markup
It is strange that the appropriate location could not be found by the tool, isn't it?
Have you ever heard if wrong rejections could be possible by this software?
http://en.wikipedia.org/wiki/Type_I_and_type_II_errors#False_positive_rate
Regards,
Markus
next reply other threads:[~2007-01-05 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 10:26 SF Markus Elfring [this message]
2007-01-05 11:21 ` Tim Waugh
2007-01-05 21:51 ` SF Markus Elfring
2007-01-06 15:03 ` SF Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2007-01-05 12:08 SF Markus Elfring
2007-01-04 8:04 SF Markus Elfring
2007-01-04 14:04 ` Tim Waugh
2007-01-04 22:04 ` SF Markus Elfring
2007-01-03 10:47 SF Markus Elfring
2007-01-03 12:43 ` Tim Waugh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1387612361@web.de \
--to=elfring@users.sourceforge.net \
--cc=patchutils-list@sourceware.org \
--cc=twaugh@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).