From: Dave Jones <davej@suse.de>
To: Justin Piszcz <war@starband.net>
Cc: Daniel Quinlan <quinlan@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 - Fixed?
Date: Mon, 25 Feb 2002 22:20:43 +0100 [thread overview]
Message-ID: <20020225222043.B27081@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0202251537080.31438-100000@freak.distro.conectiva> <Pine.LNX.4.21.0202251556140.31438-100000@freak.distro.conectiva> <6ypu2twaz3.fsf@sodium.transmeta.com> <3C7AA8F1.3F93EFB4@starband.net>
In-Reply-To: <3C7AA8F1.3F93EFB4@starband.net>; from war@starband.net on Mon, Feb 25, 2002 at 04:13:21PM -0500
On Mon, Feb 25, 2002 at 04:13:21PM -0500, Justin Piszcz wrote:
> Looks like its fixed.
>
> [root@war root]# cd /usr/src/linux-2.4.18
> [root@war linux-2.4.18]# patch -p1 < ../linux-2.4.18
> linux-2.4.18 linux-2.4.18.tar.bz2
> [root@war linux-2.4.18]# patch -p1 < ../patch-2.4.18-rc4
> patching file CREDITS
> Reversed (or previously applied) patch detected! Assume -R? [n]
Only 1 chunk got dropped, not all of rc4.
Check the rc4-final diff in testing/incr/ and apply with -R
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-02-25 21:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 18:37 Linux 2.4.18 Marcelo Tosatti
2002-02-25 18:57 ` Marcelo Tosatti
2002-02-25 20:41 ` Daniel Quinlan
2002-02-25 19:40 ` Marcelo Tosatti
2002-02-25 21:13 ` Linux 2.4.18 - Fixed? Justin Piszcz
2002-02-25 21:20 ` Dave Jones [this message]
2002-02-25 21:33 ` Linux 2.4.18 - Summary of what happened/how to fix Justin Piszcz
2002-02-25 21:53 ` Linux 2.4.18 - Don't get mad Rainer Ellinger
2002-02-25 20:09 ` Linux 2.4.18 Hugh Dickins
2002-02-25 19:03 ` Marcelo Tosatti
2002-02-25 21:45 ` Florian Weimer
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=20020225222043.B27081@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=quinlan@transmeta.com \
--cc=war@starband.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