From owner-svn-src-head@FreeBSD.ORG Fri Aug 20 01:33:43 2010 Return-Path: Delivered-To: svn-src-head@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07A0610656A8 for ; Fri, 20 Aug 2010 01:33:43 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id A0F248FC25 for ; Fri, 20 Aug 2010 01:33:42 +0000 (UTC) Received: (qmail 11146 invoked by uid 399); 20 Aug 2010 01:33:41 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 20 Aug 2010 01:33:41 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C6DDB74.3090102@FreeBSD.org> Date: Thu, 19 Aug 2010 18:33:40 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100807 Thunderbird/3.1.2 MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <201008191131.o7JBV4Yf002412@svn.freebsd.org> <4C6D18BE.2000905@fer.hr> <4C6D95A8.9070105@FreeBSD.org> <20100819213159.B48418@maildrop.int.zabbadoz.net> In-Reply-To: <20100819213159.B48418@maildrop.int.zabbadoz.net> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: svn-src-head@FreeBSD.org, Ana Kukec , svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r211501 - in head/sys: modules modules/send netinet netinet6 sys X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2010 01:33:43 -0000 On 08/19/2010 14:50, Bjoern A. Zeeb wrote: > On Thu, 19 Aug 2010, Doug Barton wrote: > >> On 08/19/2010 04:42, Ana Kukec wrote: >>> Hi all, >>> >>> A man page for the kernel side SeND, and an updated port with >>> Secure Neighbor Discovery application will follow soon. >> >> At minimum committing the man page along with new code is how such >> things should be done. Can you define "soon?" > > Yes I can: soon will be when it'll be comitted. I'm guessing that's an attempt at humor, but what I'm looking for is an actual timeline. If the answer is "in the next day or two" then that's fine, we'll let this one go with a warning. If the answer is "someday" then I'm going to request that the code be backed out until the man page(s) are done. I'm actually trying to be reasonable and work with a new developer so that they can learn how we like to have things done around here. What are you trying to do? > Meanwhile if you have time I'd know several dozen other things we > don't have a man page for ... I would definitely recommend that you make a list of them, preferably someplace visible like the wiki. If you don't already have access to the wiki (or some other suitable forum) then send the list to -doc@ and we'll make sure that it gets posted. Given the recent resurgence of interest in updating our documentation it certainly wouldn't hurt to have some examples of low-hanging fruit that we can turn budding mdoc gurus loose on. Meanwhile, the fact that in the past code has been committed without man pages is the exact cause of the problem you're describing. It is certainly not a justification for continuing to do it wrong. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso