From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: starfire update for 2.4.4-pre5
Date: Fri, 20 Apr 2001 06:55:25 -0400 [thread overview]
Message-ID: <3AE0159D.DDC3C29B@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0104200322550.5165-100000@age.cs.columbia.edu>
alas:
http://gtf.org/garzik/kernel/files/patches/2.4/2.4.4/net-version-2.4.4.5.patch.gz
To avoid all sync problems with me, you can always get the latest out of
my CVS. CVS instructions on http://sourceforge.net/projects/gkernel/
Check out module 'linux_2_4'. Branch name is based on the latest Linus
release: hack_2_4_4_pre5, hack_2_4_3, hack_2_4_2, etc. Using the branch
name is critical: you cannot simply "cvs co linux_2_4" and have things
work.
--
Jeff Garzik | The difference between America and England is that
Building 1024 | the English think 100 miles is a long distance and
MandrakeSoft | the Americans think 100 years is a long time.
| (random fortune)
next prev parent reply other threads:[~2001-04-20 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 10:28 starfire update for 2.4.4-pre5 Ion Badulescu
2001-04-20 10:55 ` Jeff Garzik [this message]
2001-04-20 11:18 ` Ion Badulescu
2001-04-28 18:54 ` Network error persists in 2.4.4 cep
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=3AE0159D.DDC3C29B@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=ionut@cs.columbia.edu \
--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