From: Muli Ben-Yehuda <mulix@mulix.org>
To: Maciej Soltysiak <solt@dns.toxicfilms.tv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: creating incremental diffs
Date: Fri, 14 Feb 2003 23:54:50 +0200 [thread overview]
Message-ID: <20030214215450.GA12233@actcom.co.il> (raw)
In-Reply-To: <Pine.LNX.4.51.0302142147360.12353@dns.toxicfilms.tv>
On Fri, Feb 14, 2003 at 09:48:16PM +0100, Maciej Soltysiak wrote:
> Hi,
>
> let's say i want to create an incremental diff between
> 2.4.21pre4aa1 and aa2.
look for a package called patchutils, which includes interdiff.
mulix@alhambra:~$ apt-cache show patchutils
Package: patchutils
[snipped]
Description: Utilities to work with patches
This package includes the following utilities:
- combinediff creates a cumulative patch from two incremental patches
- dehtmldiff extracts a diff from an HTML page
- filterdiff extracts or excludes diffs from a diff file
- fixcvsdiff fixes diff files created by CVS that "patch" mis-interprets
- flipdiff exchanges the order of two patches
- grepdiff shows which files are modified by a patch matching a regex
- interdiff shows differences between two unified diff files
- lsdiff shows which files are modified by a patch
- recountdiff recomputes counts and offsets in unified context diffs
- rediff fixes offsets and counts of a hand-edited diff
- splitdiff separates out incremental patches
- unwrapdiff demangles patches that have been word-wrapped
--
Muli Ben-Yehuda
http://www.mulix.org
http://syscalltrack.sf.net
prev parent reply other threads:[~2003-02-14 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 20:48 creating incremental diffs Maciej Soltysiak
2003-02-14 21:06 ` John Bradford
2003-02-14 21:07 ` Adrian Bunk
2003-02-14 21:24 ` Maciej Soltysiak
2003-02-14 21:22 ` Matt Reppert
2003-02-14 21:44 ` Larry McVoy
2003-02-14 21:54 ` Muli Ben-Yehuda [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=20030214215450.GA12233@actcom.co.il \
--to=mulix@mulix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solt@dns.toxicfilms.tv \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.