Greetings!
"Mike A. Harris" <[EMAIL PROTECTED]> writes:
> On Sun, 15 Oct 2000, Andre Hedrick wrote:
>
> >If they will be accepted, I will update them and maintain them.
> >I just do not have the time to run two/three trees and prepare the stuff
> >for 2.5
> >
> >> Because it is unmaintained?
Greetings!
"Mike A. Harris" [EMAIL PROTECTED] writes:
On Sun, 15 Oct 2000, Andre Hedrick wrote:
If they will be accepted, I will update them and maintain them.
I just do not have the time to run two/three trees and prepare the stuff
for 2.5
Because it is unmaintained? Once it is in
[EMAIL PROTECTED] wrote:
>
> I know it crashes some via chipsets when autotuning (IIRC), but
> if it were added behind CONFIG_EXPERIMENTAL it couldn't do any
> harm, could it?
>
> I stuck between HPT370 support in 2.4.x but non-working isdn lzs
> compression code and the reverse in 2.2.x. Just
I know it crashes some via chipsets when autotuning (IIRC), but
if it were added behind CONFIG_EXPERIMENTAL it couldn't do any
harm, could it?
I stuck between HPT370 support in 2.4.x but non-working isdn lzs
compression code and the reverse in 2.2.x. Just now I adapted Andre's
2.2.18-3 patch to
I know it crashes some via chipsets when autotuning (IIRC), but
if it were added behind CONFIG_EXPERIMENTAL it couldn't do any
harm, could it?
I stuck between HPT370 support in 2.4.x but non-working isdn lzs
compression code and the reverse in 2.2.x. Just now I adapted Andre's
2.2.18-3 patch to
[EMAIL PROTECTED] wrote:
I know it crashes some via chipsets when autotuning (IIRC), but
if it were added behind CONFIG_EXPERIMENTAL it couldn't do any
harm, could it?
I stuck between HPT370 support in 2.4.x but non-working isdn lzs
compression code and the reverse in 2.2.x. Just now I
6 matches
Mail list logo
