In message <[EMAIL PROTECTED]> Eivind Eklund writes: : I believe putting down RELENG_4 without having a finished IPv6 and : functional laptop support (I'm not sure what state this is in right : now) would be a bad idea. The laptop support is approx that of 3.x. The fe device is no longer supported as a pccard. The sn device has been added. The YE_DATA floppy device isn't supported, but could be if some is motivated to fix it. There may be a few lingering hot plug issues in the old code's migration to newbus. The newcard stuff as I've been calling it won't be stable in time, but might be functional. I'd always counted on Q1 2000 being late march rather than february. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: 4.0 code freeze scheduled for Jan 15th Jordan K. Hubbard
- Re: 4.0 code freeze scheduled for Jan 15th Warner Losh
- Re: 4.0 code freeze scheduled for Jan 15th Amancio Hasty
- Re: 4.0 code freeze scheduled for Jan 15th Ruslan Ermilov
- Re: 4.0 code freeze scheduled for Jan 15th Eivind Eklund
- Re: 4.0 code freeze scheduled for Jan 15th Alex
- Re: 4.0 code freeze scheduled for Jan 15th David O'Brien
- Re: 4.0 code freeze scheduled for Jan 15th Warner Losh
- Re: 4.0 code freeze scheduled for Jan 15th Bakul Shah
- Re: 4.0 code freeze scheduled for Jan 15th Julian Elischer
- Re: 4.0 code freeze scheduled for Jan 15th Warner Losh
- Re: 4.0 code freeze scheduled for Jan 15th Eivind Eklund
- Re: 4.0 code freeze scheduled for Jan 15th Warner Losh
- Re: 4.0 code freeze scheduled for Jan 15th David O'Brien
- Re: 4.0 code freeze scheduled for Jan 15th Brian Somers
- Re: 4.0 code freeze scheduled for Jan 15th Warner Losh
- Re: 4.0 code freeze scheduled for Jan 15th Robert Watson
- Re: 4.0 code freeze scheduled for Jan 15th Patrick Bihan-Faou
- Re: 4.0 code freeze scheduled for Jan 15th Dennis Glatting
- Re: 4.0 code freeze scheduled for Jan 15th torstenb
- Re: 4.0 code freeze scheduled for Jan 15th Rodney W. Grimes