From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 12 23:57:17 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B1D6F106566B for ; Tue, 12 Jun 2012 23:57:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 82E128FC0A for ; Tue, 12 Jun 2012 23:57:17 +0000 (UTC) Received: by dadv36 with SMTP id v36so144998dad.13 for ; Tue, 12 Jun 2012 16:57:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=RV5/WyLpznKwwEPaelvHZJpOYm8dqjgLMxMN8F+Ikvg=; b=NiXJltxceJ3WCMIEYpMbd3ghEWT6o9SsewOCOVU3QJdBdtqjuodB5Fl+gljLdIQbl/ NshTn6prt3Lsxw2dZgfqMPbJyRHB/UYhok9fiiiZS9eYvbmdN9s9XAnSNUUw3euureSF BOsXf5wgWfbmW2bf9E+zMTLo1jxYyCFG4gOYS0lfkAEX0TVVzA7GLAdV/EHOLnjfvP0Q ke7ejOwhhWAs75o9wTbIt30qnEYhIBuhaDyivxL7JKSy9Np7zQ7BWMMRvpU7T9yeJCpg hAcGBIBZ+Q6Pu2hAfgcef+gdKjAc1/X+dGsfWIuNU5/H67q25lJBmGbov5YoOkmvmoT5 nrDQ== MIME-Version: 1.0 Received: by 10.68.135.201 with SMTP id pu9mr43556045pbb.146.1339545436971; Tue, 12 Jun 2012 16:57:16 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.91.18 with HTTP; Tue, 12 Jun 2012 16:57:16 -0700 (PDT) In-Reply-To: <4FD7B8A5.9020104@zonov.org> References: <4FC6748B.5030708@zonov.org> <4FC71F13.6040008@zonov.org> <4FD60FC2.3060206@vangyzen.net> <4FD7A6D0.1080002@zonov.org> <20120612212129.GA11622@lonesome.com> <4FD7B8A5.9020104@zonov.org> Date: Tue, 12 Jun 2012 16:57:16 -0700 X-Google-Sender-Auth: XgGdxGFdm8eLfdFrJsqhMaVxQmU Message-ID: From: Adrian Chadd To: Andrey Zonov Content-Type: text/plain; charset=ISO-8859-1 Cc: Mark Linimon , Eric van Gyzen , freebsd-hackers@freebsd.org Subject: Re: usertime stale at about 371k seconds X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2012 23:57:17 -0000 Hi, The best thing IMHO to do is: * file a PR with a description of the problem, how to reproduce it, and include a patch; * then poke the maintainer directly if you know who it is; * then keep gently poking them if they forget. Having a good description of a problem, including how to reproduce it, makes it quite a bit more useful to me as a software archeologist when I want to try and understand the why behind a fix. The what may be easy to figure out, but not the original reason. Doubly so when I decide to take over a subsystem and would like to understand some of the history/evolution of the codebase. 2c, YMMV, etc Adrian