From: Beezly <beezly@beezly.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chris Funderburg <chris@directcommunications.net>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 - Full tarball is OK
Date: 25 Feb 2002 22:34:37 +0000 [thread overview]
Message-ID: <1014676477.23983.30.camel@monkey> (raw)
In-Reply-To: <E16fTkG-0006VG-00@the-village.bc.nu>
In-Reply-To: <E16fTkG-0006VG-00@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
> > FYI - The full tarball already has the missing patch...
> > So, I think, it's only patch-2.4.18 that has the problem...
>
> Argh thats the worst possible case. That means you can't do a single correct
> 2.4.18- patch
>
> If so Marcelo can you put up 2.4.18-fixed patch and a borked-fixed diff ?
If this is the case... which "version" of 2.4.18 does 2.4.19-pre1 patch
from?
I'm guessing it patches you from the "patched-from-2.4.17" release of
2.4.18? (if that makes sense)
Beezly
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-25 22:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 21:49 Linux 2.4.18 - Full tarball is OK Chris Funderburg
2002-02-25 22:37 ` Alan Cox
2002-02-25 22:32 ` Rik van Riel
2002-02-25 22:40 ` H. Peter Anvin
2002-02-25 22:49 ` Alan Cox
2002-02-25 22:34 ` Beezly [this message]
2002-02-25 22:38 ` Dan Chen
2002-02-25 23:09 ` Alan Cox
2002-02-25 22:40 ` David Rees
2002-02-25 23:02 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 21:49 Chris Funderburg
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=1014676477.23983.30.camel@monkey \
--to=beezly@beezly.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@directcommunications.net \
--cc=linux-kernel@vger.kernel.org \
/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