From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] Update make completion with gnu options
Date: Thu, 18 Jul 2013 11:21:15 +0200 [thread overview]
Message-ID: <20457.1374139275@thecus.kiddle.eu> (raw)
In-Reply-To: <29FA24CC-A523-44C7-928A-116FA209C18A@kba.biglobe.ne.jp>
"Jun T." wrote:
>
> Why the last '-f' is necessary here?
Because otherwise, most non-GNU make's will actually attempt to make
stuff. The -v enables distributed building with some implementations of
make, for example. Unlike -v, the -f option is fairly standard and
supplying it without a filename is a fairly good way to ensure that any
make will print an error and exit.
Oliver
next prev parent reply other threads:[~2013-07-18 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 6:46 Nick Cross
2013-07-12 8:38 ` Peter Stephenson
2013-07-12 23:46 ` Bart Schaefer
2013-07-13 17:00 ` Bart Schaefer
2013-07-17 15:35 ` Jun T.
2013-07-18 9:21 ` Oliver Kiddle [this message]
2013-07-18 11:44 ` Jun T.
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=20457.1374139275@thecus.kiddle.eu \
--to=okiddle@yahoo.co.uk \
--cc=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).