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: Thu, 04 Jan 2007 08:04:00 -0000 [thread overview]
Message-ID: <1386176492@web.de> (raw)
> 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
next reply other threads:[~2007-01-04 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 8:04 SF Markus Elfring [this message]
2007-01-04 14:04 ` Tim Waugh
2007-01-04 22:04 ` SF Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2007-01-05 12:08 SF Markus Elfring
2007-01-05 10:26 SF Markus Elfring
2007-01-05 11:21 ` Tim Waugh
2007-01-05 21:51 ` SF Markus Elfring
2007-01-06 15:03 ` 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=1386176492@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).