From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Calling cygpath from find exec?
Date: Tue, 01 Dec 2015 20:52:00 -0000 [thread overview]
Message-ID: <565E0882.9060408@redhat.com> (raw)
In-Reply-To: <20151201204301.GB2707@dimstar.local.net>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On 12/01/2015 01:43 PM, Duncan Roe wrote:
>> Why not just:
>>
>> find . -exec cygpath -wa {} +
>>
>> since cygpath handles more than one file in an invocation (that is,
>> using '-exec {} +' rather than '-exec {} \;' is generally faster).
>>
> I would be using xargs. Especially under /cygdrive, the "-print0 / xargs -0"
> combination takes care of spaces and other nasties in file names.
But so does 'find ... -exec ... {} +', and with one fewer process.
xargs is fine when you need it, but here, you don't.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-12-01 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 21:14 Matt D.
2015-11-23 21:16 ` Nellis, Kenneth
2015-11-23 22:31 ` Eric Blake
2015-12-01 20:43 ` Duncan Roe
2015-12-01 20:52 ` Eric Blake [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=565E0882.9060408@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).