From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 16:54:08 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9E498327 for ; Tue, 1 Jul 2014 16:54:08 +0000 (UTC) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68ACA26A1 for ; Tue, 1 Jul 2014 16:54:08 +0000 (UTC) Received: from [157.181.96.215] ([157.181.96.215]) by mail.gmx.com (mrgmxus002) with ESMTPSA (Nemesis) id 0LcjtB-1WKfTW3l4B-00k7Mw; Tue, 01 Jul 2014 18:54:06 +0200 Message-ID: <53B2E78B.9030408@gmx.com> Date: Tue, 01 Jul 2014 18:53:31 +0200 From: dt71@gmx.com User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26 MIME-Version: 1.0 To: Steve Kargl Subject: Re: freebsd and utf-8 directory names References: <3B0F582294DE3E448963BA62DC306AEE3C7F5FBCEC@exchange.mands.hu> <53B2C8B4.50306@gmx.com> <20140701153053.GA69689@troutmask.apl.washington.edu> <53B2D574.80408@gmx.com> <20140701163400.GA70109@troutmask.apl.washington.edu> In-Reply-To: <20140701163400.GA70109@troutmask.apl.washington.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:QgHG4+zYICls29Ej5JSAdhvB4yyJ68PuxV1uipJ/FINldoZ1fZn TtoMtXrEqtcmrthVo8as9GKXpcGzt18EM6uMZ33ATvF040UjdWUVTbUnFUTz3lA71vwN9uy nnAltwBvfcefjdbUEy2u13txuHfUKAWuZSDxw/8m2Ds17u8cV65qsB9xDJiFlLLK3heIqf/ X95OaqgVUWrirDadPIyUg== Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2014 16:54:08 -0000 Steve Kargl wrote, On 07/01/2014 18:34: >As far as coaching, I'll give you > the secret to how I started fixing libm: > > step 1. Obtain src/ > step 2. Read relevent files in src/ > step 3. Find problem. > step 4. Search literature. > step 5. Fix problem. > step 6. Submit patch > 6a. Receive review of patch. > 6b. Fix patch based on review. > 6c. Resubmit patch. > [[step 7. commit patch] > step 8. goto step 2. In other words, "You, the general user, should learn the art of operating system development (on your own) for the sole purpose of being able to fix the bug yourself."