[Peter Samuelson]
> Note also, if you _are_ worried about command line length limits, it's
> easy to buy yourself a lot more breathing room:
>
> cd subversion/tests/cmdline/svn-test-work; rm -fr *
Of course I meant && in place of ; there. Much safer in case the dir
itself may or may not e
[Ben Reser]
> I started this usage with r1421636. The purpose is to avoid length
> limitations
> on the argument list not spaces creating problems. We could change it to
> just:
> rm -rf subversion/tests/cmdline/svn-test-work/*
Note also, if you _are_ worried about command line length limits,
I reordered the quoted email a bit in order to make it easier to understand my
response.
On 3/3/14, 9:34 AM, Philip Martin wrote:
> The use of -mindepth 1 -maxdepth 1 is also something I don't understand,
> what advantage is there over simply using a shell expansion? Like this:
>
> rm -rf some/
On Mon, Mar 03, 2014 at 05:34:22PM +, Philip Martin wrote:
> I've been experimenting with a SPARC Solaris build recently and the
> non-portable use of find in Makefile.in is annoying, it means that the
> 'make clean' target fails. There are two uses of
>
> find some/path -mindepth 1 -maxdep
I've been experimenting with a SPARC Solaris build recently and the
non-portable use of find in Makefile.in is annoying, it means that the
'make clean' target fails. There are two uses of
find some/path -mindepth 1 -maxdepth 1 -print0 | xargs -0 rm -rf --
Solaris find doesn't support -mindepth
5 matches
Mail list logo
