From: Ivan Vadovic <pivo@pobox.sk>
To: Riley Williams <rhw@MemAlpha.CX>
Cc: linux-kernel@vger.kernel.org
Subject: Re: any good diff merging utility?
Date: Mon, 18 Jun 2001 02:34:59 +0200 [thread overview]
Message-ID: <20010618023459.C1063@ivan.doma> (raw)
In-Reply-To: <20010618014547.B1063@ivan.doma> <Pine.LNX.4.33.0106180102520.25038-100000@infradead.org>
In-Reply-To: <Pine.LNX.4.33.0106180102520.25038-100000@infradead.org>; from rhw@MemAlpha.CX on Mon, Jun 18, 2001 at 01:06:54AM +0100
> > I like to build kernels with a bunch of patches on top to test
> > new stuff. The problem is that it takes a lot of effort to fix
> > all the failed hunks during patching that really wouldn't have
> > to be failed if only patch was a little more inteligent and
> > could merge several patches into one ( if possible) or if could
> > take into account already applied patches.
>
> The basic problem here is that the "failed hunks" are usually there
> because of conflicts between the two patches in question, and as a
> result, they are not as easy to merge automagically as one might at
> first assume.
Very often the case is that they indeed can be merged automagically.
For example two patches inserting few lines right after the #include
lines.
patch1:
@@ 10,1 10,2 @@
#include <foo.h>
+#include <1.h>
patch2:
@@ 10,1 10,2 @@
#include <foo.h>
+#include <2.h>
The patch will fail to patch :-). But there is no real conflict between
the patches.
> > Well, are there any utilities to merge diffs? I couldn't find
> > any on freshmeat. So what are you using to stack many patches
> > onto the kernel tree? Just manualy modify the diff? I'll try to
> > write something more automatic if nothing comes up.
>
> I once came across a utility called "diff3" that was designed to take
> a patch for one version of a package and create an equivalent patch
> for another version of the same package, but I haven't been able to
> find it again since my hard drive crashed.
diff3 comes from gnu diffutils
<ftp://ftp.gnu.org/gnu/diffutils/diffutils-2.7.tar.gz>. But all it does
is comparing three FILES for differencies.
Ivan Vadovic
next prev parent reply other threads:[~2001-06-18 0:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-17 23:45 Ivan Vadovic
2001-06-18 0:06 ` Riley Williams
2001-06-18 0:34 ` Ivan Vadovic [this message]
2001-06-18 7:26 ` Geert Uytterhoeven
2001-06-18 23:36 ` Riley Williams
2001-06-18 0:41 ` Jonathan Lundell
2001-06-18 0:51 ` Keith Owens
2001-06-18 4:20 ` Paul Mackerras
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=20010618023459.C1063@ivan.doma \
--to=pivo@pobox.sk \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.CX \
/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
all inboxes | Powered by JetHome®