From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 17:09:05 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 B5DE1973 for ; Tue, 1 Jul 2014 17:09:05 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask.apl.washington.edu", Issuer "troutmask.apl.washington.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 795FB27E5 for ; Tue, 1 Jul 2014 17:09:05 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id s61H94Bq070342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 1 Jul 2014 10:09:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id s61H94FE070341; Tue, 1 Jul 2014 10:09:04 -0700 (PDT) (envelope-from sgk) Date: Tue, 1 Jul 2014 10:09:04 -0700 From: Steve Kargl To: dt71@gmx.com Subject: Re: freebsd and utf-8 directory names Message-ID: <20140701170904.GA70304@troutmask.apl.washington.edu> 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> <53B2E78B.9030408@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53B2E78B.9030408@gmx.com> User-Agent: Mutt/1.5.23 (2014-03-12) 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 17:09:05 -0000 On Tue, Jul 01, 2014 at 06:53:31PM +0200, dt71@gmx.com wrote: > 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." No. In other words, "If fixing the bug is so important to you that it must be fixed, then perhaps, you should take the initiative to learn enough to fix the bug." Or, in other other words, "Give a man a fish, he eats for a day; teach a man to fish, he eats for a lifetime." Finally, as a general user, it is often counter-productive to include vailed invectives in your emails to a public list. See for example: "Poke the FreeBSD developers to start fixing bugs, maybe (but not very likely) that will help." Sheesh, as if FreeBSD developer never fix any bugs. -- Steve