From: Alan Cox <alan@redhat.com>
To: szepe@pinerecords.com (Tomas Szepe)
Cc: alan@redhat.com (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21-ac4
Date: Fri, 27 Jun 2003 14:38:26 -0400 (EDT) [thread overview]
Message-ID: <200306271838.h5RIcQh13694@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030627183633.GD21564@louise.pinerecords.com> from "Tomas Szepe" at Meh 27, 2003 08:36:33
> $ ls -la patch-2.4.21-ac[34].gz
> -rw-r--r-- 1 kala users 2891908 Jun 25 18:32 patch-2.4.21-ac3.gz
> -rw-r--r-- 1 kala users 2891908 Jun 27 20:07 patch-2.4.21-ac4.gz
> $ diff patch-2.4.21-ac[34].gz
Intriguing. The joys of caching. Will go fix
prev parent reply other threads:[~2003-06-27 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 18:11 Alan Cox
2003-06-27 18:36 ` Tomas Szepe
2003-06-27 18:38 ` Alan Cox [this message]
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=200306271838.h5RIcQh13694@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®