From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-rc1-ac5
Date: 15 Jul 2002 16:14:08 -0700 [thread overview]
Message-ID: <agvl00$jjm$1@cesium.transmeta.com> (raw)
In-Reply-To: 20020715220241Z317668-685+9887@vger.kernel.org
Followup to: <20020715220241Z317668-685+9887@vger.kernel.org>
By author: Rudmer van Dijk <rvandijk@science.uva.nl>
In newsgroup: linux.dev.kernel
>
> On Monday 15 July 2002 23:48, Alan Cox wrote:
> > Linux 2.4.19rc1-ac5
>
> it looks like the file is damaged:
>
> # gzip -t patch-2.4.19-rc1-ac5.gz
> gzip: patch-2.4.19-rc1-ac5.gz: invalid compressed data--format violated
>
> waiting for the .bz2 file...
>
The file on zeus.kernel.org is just fine. Problem is on your end.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-07-15 23:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 21:48 Linux 2.4.19-rc1-ac5 Alan Cox
2002-07-15 22:10 ` Rudmer van Dijk
2002-07-15 23:14 ` H. Peter Anvin [this message]
2002-07-15 23:25 ` Robert Love
2002-07-16 0:28 ` Alan Cox
2002-07-15 23:21 ` H. Peter Anvin
2002-07-15 23:29 ` Robert Love
2002-07-15 23:47 ` H. Peter Anvin
2002-07-16 6:46 ` Rudmer van Dijk
2002-07-16 4:01 ` Linux 2.4.19-rc1-ac5 -- Build error in mpparse.c Miles Lane
2002-07-16 4:14 ` Brandon Low
2002-07-16 7:54 ` Linux 2.4.19-rc1-ac5 -- Build error in mpparse.c (possible fix) khromy
2002-07-16 8:07 ` khromy
2002-07-16 10:09 ` Alan Cox
2002-07-16 11:45 ` Linux 2.4.19-rc1-ac5 Kasper Dupont
2002-07-16 17:07 ` Andre Hedrick
2002-07-16 17:13 ` Alan Cox
2002-07-19 20:36 ` Linux 2.4.19-rc2-ac2 Ian Soboroff
2002-07-19 21:02 ` Philippe Gramoullé
2002-07-22 13:03 ` mbs
2002-07-17 17:11 ` Linux 2.4.19-rc1-ac5 Kasper Dupont
2002-07-28 23:06 ` Kasper Dupont
2002-07-29 12:00 ` Alan Cox
2002-07-29 13:58 ` Kasper Dupont
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='agvl00$jjm$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 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.