Daniel Eischen <[EMAIL PROTECTED]> writes: > Just tell me what to do, and I'll do it :-) I won't go that far, but I'd suggest keeping the versions in -current and -stable in sync (after testing new stuff in -current, of course). There's (yet) no technical reason not to do so and it makes maintenance much easier. tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- new seg fault in thread code Kip Macy
- Re: seg fault in mutex_queue_enq Thomas Gellekum
- Re: seg fault in mutex_queue_enq Daniel Eischen
- Re: seg fault in mutex_queue_enq Daniel Eischen
- Re: seg fault in mutex_queue_enq Thomas Gellekum
- Re: seg fault in mutex_queue_enq Thomas Gellekum
- Re: seg fault in mutex_queue_enq Jordan K. Hubbard
- Re: seg fault in mutex_queue_enq Mike Meyer
- Re: seg fault in mutex_queue_enq Daniel Eischen
- Re: seg fault in mutex_queue_enq Jordan K. Hubbard
- Thomas Gellekum