From owner-freebsd-hackers Sun May 16 14:58:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles551.castles.com [208.214.165.115]) by hub.freebsd.org (Postfix) with ESMTP id BE97014C91 for ; Sun, 16 May 1999 14:58:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA08351; Sun, 16 May 1999 14:43:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905162143.OAA08351@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: kip@lyris.com Cc: hackers@freeBSD.org Subject: Re: problems with recursion in libc_r In-reply-to: Your message of "Sun, 09 May 1999 16:17:30 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 May 1999 14:43:42 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Should I actually think about changes to make, or should I simply hold off > and let more experienced kernel hackers take care of the fixes? If you have the time and motivation to produce changes, please do indeed do so. You'll achieve best results by establishing a relationship with one or more committers, so that you have a direct vector for having your changes tested and committed. > However, before I start making any modifications to FreeBSD I would like > to know that the changes I make will actually be incorporated, so that I > will not suffer the same fate as PAO, namely having to reincorporate my > changes each new release. If you work with us, rather than developing in isolation, there is little danger of this. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message