From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org, Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH v2] Makefile: fix "make clean" for old GNU find
Date: Mon, 12 Mar 2012 15:08:30 +0200 [thread overview]
Message-ID: <1331557710.12037.10.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1331315349-8541-1-git-send-email-computersforpeace@gmail.com>
On Fri, 2012-03-09 at 09:49 -0800, Brian Norris wrote:
> findutils v4.1.x does not have the `-exec CMD {} +' syntax. We can just as
> easily use the `-exec CMD {} \;' syntax. However, it will launch a lot more
> `rm' processes, so we only use it if the first form fails with an error.
> This isn't a perfect solution (`find -exec +' can fail for other reasons)
> but it works well enough.
>
> This problem manifests itself in RHEL 4, findutils 4.1.20:
Pushed, thanks you!
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2012-03-12 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 17:49 [PATCH v2] Makefile: fix "make clean" for old GNU find Brian Norris
2012-03-09 21:14 ` Mike Frysinger
2012-03-12 13:08 ` Artem Bityutskiy [this message]
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=1331557710.12037.10.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox