From: SF Markus Elfring <elfring@users.sourceforge.net>
To: patchutils-list@sourceware.org
Subject: How to resolve hiccups by patch program?
Date: Wed, 03 Jan 2007 10:47:00 -0000 [thread overview]
Message-ID: <1384971006@web.de> (raw)
Hello,
I wish you a happy new year.
I have found the article "http://gnuarch.org/gnuarchwiki/Process_*.rej_files" that references experiences by Miles Bader. I find his statement "Applying a hunk from diff-mode sometimes succeeds where patch failed." interesting in my case. Can Emacs perform an update really better than other usual tools in any special situations?
A couple of tools are mentioned on the page "http://cyberelk.net/tim/patchutils/". It seems that I am looking for an option or feature that might not be available here so far.
Can a package of reject files be converted by an other program into another change set for a second try if anything went unexpectedly wrong? (Does this approach make sense?)
How much may I trust the applicability of patches that were generated by TortoiseSVN 1.4.1.7992 compared to other command line tools?
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
Regards,
Markus
next reply other threads:[~2007-01-03 10:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 10:47 SF Markus Elfring [this message]
2007-01-03 12:43 ` Tim Waugh
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=1384971006@web.de \
--to=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).