From owner-freebsd-ports Thu Sep 17 16:46:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05525 for freebsd-ports-outgoing; Thu, 17 Sep 1998 16:46:38 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05384 for ; Thu, 17 Sep 1998 16:46:05 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca5-24.ix.netcom.com [209.109.234.24]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id QAA07694; Thu, 17 Sep 1998 16:45:26 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id QAA16114; Thu, 17 Sep 1998 16:45:22 -0700 (PDT) Date: Thu, 17 Sep 1998 16:45:22 -0700 (PDT) Message-Id: <199809172345.QAA16114@silvia.hip.berkeley.edu> To: axl@iafrica.com CC: ports@FreeBSD.ORG In-reply-to: <8090.906036015@axl.training.iafrica.com> (message from Sheldon Hearn on Thu, 17 Sep 1998 14:40:15 +0200) Subject: Re: Contents of patchfiles From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * I'd like to know how the PortsMeisters feel about my doing this for * ports submissions. The gain is that users and future tinkers alike will * be able to see, at a glance, what a patch is supposed to do. The loss is * in disk space. The tradeoff is actually not in disk space (who cares about a few dozen bytes? :) but in human labor in the future as whoever fixes the port will have to hand-edit the patch to add it back. That said, it's certainly fine for me. (I edit patches all the time anyway.) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message