public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation•org>
To: Joe Perches <joe@perches•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Masahiro Yamada <yamada.masahiro@socionext•com>,
	Randy Dunlap <rdunlap@infradead•org>,
	Mark Brown <broonie@kernel•org>,
	linux-fsdevel@vger•kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	linux-mm@kvack•org,
	Linux-Next Mailing List <linux-next@vger•kernel.org>,
	mhocko@suse•cz, mm-commits@vger•kernel.org,
	Michal Wajdeczko <michal.wajdeczko@intel•com>,
	Daniel Vetter <daniel.vetter@ffwll•ch>,
	Jani Nikula <jani.nikula@linux•intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux•intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel•com>,
	Intel Graphics <intel-gfx@lists•freedesktop.org>,
	DRI <dri-devel@lists•freedesktop.org>,
	Chris Wilson <chris@chris-wilson•co.uk>
Subject: Re: mmotm 2019-07-04-15-01 uploaded (gpu/drm/i915/oa/)
Date: Thu, 4 Jul 2019 22:29:06 -0700	[thread overview]
Message-ID: <20190704222906.f817d02cb248561edd84a669@linux-foundation.org> (raw)
In-Reply-To: <5f4680cce78573ecfbbdc0dfca489710581b966f.camel@perches.com>

On Thu, 04 Jul 2019 22:22:41 -0700 Joe Perches <joe@perches•com> wrote:

> > So when comparing a zero-length file with a non-existent file, diff
> > produces no output.
> 
> Why use the -N option ?
> 
> $ diff --help
> [...]
>   -N, --new-file                  treat absent files as empty
> 
> otherwise
> 
> $ cd $(mktemp -d -p .)
> $ touch x
> $ diff -u x y
> diff: y: No such file or directory

Without -N diff fails and exits with an error.  -N does what's desired
as long as the non-missing file isn't empty.



  reply	other threads:[~2019-07-05  5:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 22:01 mmotm 2019-07-04-15-01 uploaded akpm
2019-07-05  1:09 ` mmotm 2019-07-04-15-01 uploaded (gpu/drm/i915/oa/) Randy Dunlap
2019-07-05  1:19   ` Randy Dunlap
2019-07-05  3:05   ` Masahiro Yamada
2019-07-05  3:09     ` Masahiro Yamada
2019-07-05  3:23       ` Randy Dunlap
2019-07-05  3:44         ` Masahiro Yamada
2019-07-05  4:09           ` Randy Dunlap
2019-07-31 13:21           ` Jani Nikula
2019-07-05  3:14     ` Stephen Rothwell
2019-07-05  5:09       ` Andrew Morton
2019-07-05  5:22         ` Joe Perches
2019-07-05  5:29           ` Andrew Morton [this message]
2019-07-05  3:01 ` mmotm 2019-07-04-15-01 uploaded (mm/vmscan.c) Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190704222906.f817d02cb248561edd84a669@linux-foundation.org \
    --to=akpm@linux-foundation$(echo .)org \
    --cc=broonie@kernel$(echo .)org \
    --cc=chris@chris-wilson$(echo .)co.uk \
    --cc=daniel.vetter@ffwll$(echo .)ch \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=intel-gfx@lists$(echo .)freedesktop.org \
    --cc=jani.nikula@linux$(echo .)intel.com \
    --cc=joe@perches$(echo .)com \
    --cc=joonas.lahtinen@linux$(echo .)intel.com \
    --cc=linux-fsdevel@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mm@kvack$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mhocko@suse$(echo .)cz \
    --cc=michal.wajdeczko@intel$(echo .)com \
    --cc=mm-commits@vger$(echo .)kernel.org \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=rodrigo.vivi@intel$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=yamada.masahiro@socionext$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox