From: Joe <joeja@mindspring.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Michael Peddemors <michael@wizard.ca>, linux-kernel@vger.kernel.org
Subject: Re: loop back broken in 2.2.14
Date: Thu, 15 Nov 2001 20:52:29 -0800 [thread overview]
Message-ID: <3BF49B8D.3C416328@mindspring.com> (raw)
In-Reply-To: <Springmail.105.1005761843.0.30236800@www.springmail.com> <1005860255.9913.794.camel@mistress> <20011116003126.C1735@werewolf.able.es>
Well I think it is a good idea to do this and have errata patches or something. I don't think Linus wants the extra work. I'd do it myself, but I don't have the ftp storage space, the time or the bandwidth. I am now keeping seperate trees on my box. One that is the default kernel and then my tree which has fixes to that tree. I'll be working out a
system of testing and migration now ..................
> Well, Linus could post a 'errata' patch...
> Layout now in ftp space is (reverse date order):
>
> test-kernels
> ChangeLog-2.4.14
> LATEST-IS-2.4.14
> linux-2.4.14.tar.bz2
next prev parent reply other threads:[~2001-11-16 4:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 18:17 Re: Re: loop back broken in 2.2.14 joeja
2001-11-15 21:37 ` Michael Peddemors
2001-11-15 23:31 ` J.A. Magallon
2001-11-16 4:52 ` Joe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-15 23:38 Mr R A Mercer
2001-11-12 17:40 joeja
2001-11-12 20:41 ` J Sloan
2001-11-11 21:27 Joe
2001-11-11 21:35 ` François Cami
2001-11-11 21:38 ` Jeff Garzik
2001-11-11 22:28 ` J Sloan
2001-11-11 22:55 ` J Sloan
2001-11-11 21:36 ` elko
2001-11-11 21:55 ` Adrian Bunk
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=3BF49B8D.3C416328@mindspring.com \
--to=joeja@mindspring.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@wizard.ca \
/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.