From: Tim Waugh <twaugh@redhat.com>
To: John Weber <weber@nyc.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linus vs. AC kernels
Date: Wed, 4 Jul 2001 18:14:52 +0100 [thread overview]
Message-ID: <20010704181452.L5254@redhat.com> (raw)
In-Reply-To: <3B434B1A.1070809@nyc.rr.com>
In-Reply-To: <3B434B1A.1070809@nyc.rr.com>; from weber@nyc.rr.com on Wed, Jul 04, 2001 at 12:58:02PM -0400
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
On Wed, Jul 04, 2001 at 12:58:02PM -0400, John Weber wrote:
> Is there any way to find out up to what ac# level has been merged with
> the current kernel releases (including the pre kernels)?
You can get a diff between two arbitrary patches against the same
thing using interdiff from patchutils. For example:
interdiff -h <(bzcat patch-2.4.6-pre5) <(bzcat patch-2.4.5-ac24.bz2)
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-07-04 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 16:58 Linus vs. AC kernels John Weber
2001-07-04 17:14 ` Tim Waugh [this message]
[not found] <Pine.LNX.4.33.0107041208500.5733-100000@eax.student.umd.edu>
2001-07-04 17:06 ` John Weber
2001-07-04 17:17 ` Alan Cox
2001-07-06 19:18 ` David Schwartz
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=20010704181452.L5254@redhat.com \
--to=twaugh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=weber@nyc.rr.com \
/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.