From: Adrian Bunk <bunk@fs.tum.de>
To: Maciej Soltysiak <solt@dns.toxicfilms.tv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: creating incremental diffs
Date: Fri, 14 Feb 2003 22:07:54 +0100 [thread overview]
Message-ID: <20030214210754.GN20159@fs.tum.de> (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,
Hi Maciej,
> let's say i want to create an incremental diff between
> 2.4.21pre4aa1 and aa2.
>
> how do i do that?
install Tim Waugh's patchutils [1] and do an
interdiff -z 2.4.21pre4aa1.gz 2.4.21pre4aa2.gz > my-aa1-aa2
> Regards,
> Maciej Soltysiak
cu
Adrian
[1] http://cyberelk.net/tim/data/patchutils/
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-02-14 21:00 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 [this message]
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
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=20030214210754.GN20159@fs.tum.de \
--to=bunk@fs.tum.de \
--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.