public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Robin Johnson <robbat2@fermi.orbis-terrarum.net>
Cc: Adrian Bunk <bunk@fs.tum.de>, linux-kernel@vger.kernel.org
Subject: Re: Incremental Patch Building Script
Date: Sat, 20 Apr 2002 00:16:36 +0100	[thread overview]
Message-ID: <20020420001636.I16947@redhat.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0204161404310.12986-100000@mimas.fachschaften.tu-muenchen.de> <Pine.LNX.4.43.0204160710290.12000-100000@fermi.orbis-terrarum.net>

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

On Tue, Apr 16, 2002 at 07:11:46AM -0700, Robin Johnson wrote:

> On Tue, 16 Apr 2002, Adrian Bunk wrote:
> >
> > There's already interdiff from Tim Waugh's patchutils [1] that makes
> > incremental diffs between patches. And interdiff doesn't need the source
> > the patches are against (IOW: to make an incremental patch between two
> > kernel -pre patches you don't need any kernel sources). It's pretty
> > simple:
> >
> >   interdiff -z patch-2.4.19-pre6.gz patch-2.4.19-pre7.gz > mydiff
> 
> I did try interdiff before writing this script, and it wasn't generating
> the right output.

I think that the problems Robin was seeing are resolved in
patchutils-0.2.12.

(The output was correct, but needlessly lengthy.)

Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      parent reply	other threads:[~2002-04-19 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 10:04 Incremental Patch Building Script Robin Johnson
2002-04-16 12:10 ` Adrian Bunk
2002-04-16 14:11   ` Robin Johnson
2002-04-16 15:14     ` Tim Waugh
2002-04-19 23:16     ` Tim Waugh [this message]

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=20020420001636.I16947@redhat.com \
    --to=twaugh@redhat.com \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robbat2@fermi.orbis-terrarum.net \
    /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