Date: Sat, 23 May 2020 14:21:07 +0300 From: Yuri Pankov <ypankov@fastmail.com> To: Fehmi Noyan ISI <fnoyanisi@yahoo.com>, freebsd-hackers@freebsd.org Subject: Re: diff(1) -N behaviour - Bug 233402 Message-ID: <94a82a22-b5c9-b797-30cc-0242f6da1c8a@fastmail.com> In-Reply-To: <B380BAF4-2343-4A22-A26D-13437ECC00C2@yahoo.com> References: <B380BAF4-2343-4A22-A26D-13437ECC00C2.ref@yahoo.com> <B380BAF4-2343-4A22-A26D-13437ECC00C2@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Fehmi Noyan ISI via freebsd-hackers wrote: > Hiya > > Apparently, after we switched from GNU diff to BSD diff, the -N flag no longer assumes absent files as empty. > There is a bug report about GNU diff compatibility but when I look at diff(1) man page, I see that not treating absent files as empty is intentional rather than a missing functionality. > > If this is not the case, I can work on patch to match to GNU diff behaviour, otherwise, this bug report can be closed I think. > > What’s your take on this? > > -N --new-file > If a file is found in only one directory, act as if it was found > in the other directory too but was of zero size. > > man for GNU diff > -N, --new-file > treat absent files as empty I think both descriptions say the same, i.e. "zero size" == "empty"?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?94a82a22-b5c9-b797-30cc-0242f6da1c8a>