From owner-freebsd-ports Sun Sep 26 18:32:19 1999 Delivered-To: freebsd-ports@freebsd.org Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (Postfix) with ESMTP id D01C415382 for ; Sun, 26 Sep 1999 18:32:16 -0700 (PDT) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca50-92.ix.netcom.com [209.111.213.92]) by vader.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id SAA15360; Sun, 26 Sep 1999 18:28:56 -0700 (PDT) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id SAA09859; Sun, 26 Sep 1999 18:28:38 -0700 (PDT) To: Doug Cc: Will Andrews , ports@FreeBSD.ORG Subject: Re: Help with RCS files, patches, and PR's required. References: <37EE876F.19C6F5@gorean.org> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 26 Sep 1999 18:28:27 -0700 In-Reply-To: Doug's message of "Sun, 26 Sep 1999 13:51:59 -0700" Message-ID: Lines: 13 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Doug * I think it's a ports thing. I see the request for context diffs most * often on the ports list, although it might be a few vocal developers * trying to gain momentum for their cause. :) That's actually the opposite. I believe it's the syntax of ports Makefiles that makes patches easier to read with unified diffs, since it's mostly a series of variable definitions sorted by category, as opposed to a C source file, where there is more context around each changed lines. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message