From: Tim Waugh <twaugh@redhat.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: patchutils-list@sourceware.org
Subject: Re: How to resolve hiccups by patch program?
Date: Wed, 03 Jan 2007 12:43:00 -0000 [thread overview]
Message-ID: <1167828208.4565.5.camel@cyberelk.elk> (raw)
In-Reply-To: <1384971006@web.de>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Wed, 2007-01-03 at 11:47 +0100, SF Markus Elfring wrote:
> I wish you a happy new year.
And to you.
> I ask because the technical details might be relevant for the open issue "Improve const-correctness" (http://bugs.digium.com/view.php?id=8160) with the Asterisk software. Would you like to share any more ideas for a solution to the observed obstacle?
> http://article.gmane.org/gmane.comp.version-control.subversion.tortoisesvn.user/5180
I have yet to see a patch reject that was created by patch(1) without
good reason. There are sure to be conflicts of some sort in the patch.
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.
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-03 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 10:47 SF Markus Elfring
2007-01-03 12:43 ` Tim Waugh [this message]
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-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-05 12:08 SF Markus Elfring
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=1167828208.4565.5.camel@cyberelk.elk \
--to=twaugh@redhat.com \
--cc=elfring@users.sourceforge.net \
--cc=patchutils-list@sourceware.org \
/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).