From owner-freebsd-doc@FreeBSD.ORG Fri Aug 20 14:33:08 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A8B616A4CE; Fri, 20 Aug 2004 14:33:08 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 142A143D1F; Fri, 20 Aug 2004 14:33:08 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id 22EB669A8C; Fri, 20 Aug 2004 10:33:07 -0400 (EDT) Date: Fri, 20 Aug 2004 10:33:06 -0400 From: Bill Moran To: Marc Fonvieille Message-Id: <20040820103306.5f0ffb6f.wmoran@potentialtech.com> In-Reply-To: <20040820133029.GE63041@abigail.blackend.org> References: <20040820133029.GE63041@abigail.blackend.org> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-doc@freebsd.org Subject: Re: To PR Senders X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2004 14:33:08 -0000 Marc Fonvieille wrote: > Hello, > > As everyone knows, sending a PR is the best way to help us to fix a > documentation issue. When you send a PR and you have a patch to fix the > problem, you should *attach* the patch with the PR and *not* just provide a > URL. > > With a URL, the PR database will not contain your submission, it will > be difficult for us to read the PR, it will be difficult for us to work > on your submission via PR feedback, etc. So, please attach your > patches. > > Thanks for the listening :) There is some problematic ambiguity to this request. Section 4.3 of the article on submitting problem reprts: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/pr-writing.html states "Also note that while including small patches in a PR is generally all right--particularly when they fix the problem described in the PR--large patches and especially new code which may require substantial review before committing should be placed on a web or ftp server" While I agree with everything that's been stated here (both in your email Marc, as well as the article) the question for anyone submitting a PR becomes: "Based on these recommendations, do I attach it or post it?" The best advice I've heard so far was (unfortunately) relegated to PS status in your email: > PS: Of course do not send your 1MB patch :)) So, now I know that patches of 1M or larger are not attached, while those of smaller size may(?) be attached ;) Fact is, I don't _really_ know what the upper limit is (size-wise) for attaching vs. posting. And the reference to "new code/substantial review" is (unfortunately) even more ambiguous! I guess what I'm saying is that for someone like myself (who has and intends to continue submitting patches, but has never been on the other side of PR handling) it's difficult to know what the best way to submit a patch is. My goal as a patch submitter is to make the job of the comitter as easy as possible, so he/she can focus on the _content_ of my patch, not the steps required to extract and unmangle it. I don't have the knowledge to make exact recommendations, but perhaps a documented rule of thumb along these lines would help: "Patches in excess of 200k, or which contain over 50 lines of completely new content, should not be attached to the PR, but should be placed on an ftp/web server and the URL included. Patches below these limits should always be attached to the PR." I understand that it may be difficult to reach a consensus on exactly what limits to set, but I think it would make things a little clearer for folks like me. Hope these musings are useful. -- Bill Moran Potential Technologies http://www.potentialtech.com