Date: Sat, 14 Feb 1998 05:48:46 -0800 (PST) From: asami@cs.berkeley.edu (Satoshi Asami) To: sprice@HiWAAY.net Cc: brian@Awfulhak.org, ports@FreeBSD.ORG Subject: Re: ftp://freebsd.org - RIP Message-ID: <199802141348.FAA00179@silvia.HIP.Berkeley.EDU> In-Reply-To: <34E3BC84.3F54BC7E@hiwaay.net> (message from Steve Price on Thu, 12 Feb 1998 21:22:44 -0600)
next in thread | previous in thread | raw e-mail | index | archive | help
* Yes it can be in any format. I happen to prefer unified diffs * because they are easier for me to fix tab->space expansions among * other things. My personal preference only. Yes, it's usually easier to read (although there are exceptions...some C programs look pretty bad in unidiff), and almost always easier to fix. Especially when there is a one-line change that I want to negate (like diffs that change "$Id: ..." to "$Id$"), it's a simple matter of "yypr+jdd" or "r jdd" (that's vi-speak). As for the handbook, it doesn't say unidiff or context diff explicitly, but it gives "diff -ruN" as the example on how to create recursive diffs. It seems most ports people prefer unidiff, so I'll add a note about unidiff generally making people happier. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802141348.FAA00179>