From: CaT <cat@zip.com.au>
To: "Garst R. Reese" <reese@isn.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.17-pre4 extra-version
Date: Thu, 6 Dec 2001 11:15:50 +1100 [thread overview]
Message-ID: <20011206111550.L983@zip.com.au> (raw)
In-Reply-To: <3C0EB178.4A599A31@isn.net> <20011205155509.B9588@figure1.int.wirex.com>
In-Reply-To: <20011205155509.B9588@figure1.int.wirex.com>
On Wed, Dec 05, 2001 at 03:55:09PM -0800, Chris Wright wrote:
> * Garst R. Reese (reese@isn.net) wrote:
> > It really does help to keep extra version uptodate ;)
>
> seem fine to me...
It didn't happen for me.
What's the size of your pre4 patch?
--
CaT - A high level of technology does not a civilisation make.
next prev parent reply other threads:[~2001-12-06 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 23:44 2.4.17-pre4 extra-version Garst R. Reese
2001-12-05 23:55 ` Chris Wright
2001-12-06 0:15 ` CaT [this message]
2001-12-06 1:30 ` Garst R. Reese
2001-12-06 0:11 ` André Dahlqvist
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=20011206111550.L983@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=reese@isn.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