From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8639 invoked by alias); 4 Jan 2007 08:04:34 -0000 Received: (qmail 8584 invoked by uid 22791); 4 Jan 2007 08:04:32 -0000 X-Spam-Status: No, hits=2.5 required=5.0 tests=AWL,BAYES_20,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org Received: from fmmailgate06.web.de (HELO fmmailgate06.web.de) (217.72.192.247) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 04 Jan 2007 08:04:24 +0000 Received: from web.de by fmmailgate06.web.de (Postfix) with SMTP id 9C7792F2; Thu, 4 Jan 2007 09:04:21 +0100 (CET) Received: from [62.217.57.165] by freemailng5202.web.de with HTTP; Thu, 04 Jan 2007 09:04:21 +0100 Date: Thu, 04 Jan 2007 08:04:00 -0000 Message-Id: <1386176492@web.de> MIME-Version: 1.0 From: SF Markus Elfring To: Tim Waugh Cc: patchutils-list@sourceware.org Subject: Re: How to resolve hiccups by patch program? Organization: http://freemail.web.de/ X-Sender: markus.elfring@web.de Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact patchutils-list-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: patchutils-list-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00002.txt.bz2 > 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