Date: Tue, 12 Jun 2012 16:57:16 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Andrey Zonov <andrey@zonov.org> Cc: Mark Linimon <linimon@lonesome.com>, Eric van Gyzen <eric@vangyzen.net>, freebsd-hackers@freebsd.org Subject: Re: usertime stale at about 371k seconds Message-ID: <CAJ-Vmon%2BpZ=YoVsnd07kPzqCyaJnJLvENRQZOFa766V%2B0E=V9A@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmon%2BpZ=YoVsnd07kPzqCyaJnJLvENRQZOFa766V%2B0E=V9A>