From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-rc1-ac5
Date: Mon, 15 Jul 2002 16:21:39 -0700 [thread overview]
Message-ID: <3D335903.6000603@zytor.com> (raw)
In-Reply-To: 1026779299.32689.46.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
>
>>The file on zeus.kernel.org is just fine. Problem is on your end.
> I fixed the file on zeus - it was originally wrong.
>
Hmmm...
This bothers me somewhat, because a .bz2 file should not have been
created if the .gz file was corrupt, but the original poster strongly
implied that he had both the .gz file and a .bz2 file, unless your
update came in between.
-hpa
next prev parent reply other threads:[~2002-07-15 23:19 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
2002-07-15 23:25 ` Robert Love
2002-07-16 0:28 ` Alan Cox
2002-07-15 23:21 ` H. Peter Anvin [this message]
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=3D335903.6000603@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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