make check-expensive [was: [PATCH] rm, du, chmod, chown, chgrp: use much less memory for large directories]

On 08/24/2011 10:49 AM, Jim Meyering wrote: Voelker, Bernhard wrote: BTW: Wouldn't this test deserve a proper make target, e.g. make check-expensive? Yes, good idea. That would make it easier to run just those test. However, hard-coding the list of expensive and very-expensive tests would

xargs: errno-buffer read failed in xargs_do_exec

The message comes if the parallelism of xargs is increased/decreased several times in a short time. Test case (OpenSuSE 11.4, ext4, xargs from git): mkdir /tmp/test cd /tmp/test dd if=/dev/zero of=1M bs=1M count=1 seq 4000 | ~/git/findutils/inst/bin/xargs -P 2 -n 1 cp 1M pid=$! sleep 1 while

[bug #37683] -inum doesn't work on ext4 file systems with find 4.5.10

is the latest version on ftp.gnu.org still 4.4.2 (3.5 years old) while distros already use newer versions? Have a nice day, Berny From 3a1f9a36a32814448891f4b3e82d358336afadb9 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker m...@bernhard-voelker.de Date: Mon, 12 Nov 2012 19:29:45 +0100 Subject: [PATCH] Fix

Re: [bug #37683] -inum doesn't work on ext4 file systems with find 4.5.10

On 11/13/2012 01:20 AM, James Youngman wrote: On Mon, Nov 12, 2012 at 6:35 PM, Bernhard Voelker m...@bernhard-voelker.de wrote: [please CC me, as I'm not subscribed] ... BTW: Why is the latest version on ftp.gnu.org still 4.4.2 (3.5 years old) while distros already use newer versions

Re: [bug #37683] -inum doesn't work on ext4 file systems with find 4.5.10

On 11/16/2012 10:46 PM, James Youngman wrote: On Tue, Nov 13, 2012 at 6:07 AM, Bernhard Voelker m...@bernhard-voelker.de wrote: On 11/13/2012 01:20 AM, James Youngman wrote: On Mon, Nov 12, 2012 at 6:35 PM, Bernhard Voelker m...@bernhard-voelker.de wrote: BTW: Why is the latest version

Re: [bug #37811] Mismatch of messages given by `find --help' and its real execution result.

argument'. What about the following? Have a nice day, Berny From 3e3d398295ff78516fa9251e8a1857004caaf0ed Mon Sep 17 00:00:00 2001 From: Bernhard Voelker m...@bernhard-voelker.de Date: Mon, 26 Nov 2012 23:42:12 +0100 Subject: [PATCH] find: improve diagnostic for not built-in arguments of -type * find

Re: -inum doesn't work on ext4 file systems with find 4.5.10

On 12/14/2012 11:55 PM, James Youngman wrote: I have pushed an alternative patch. It is more complex but I hope more efficient. It's described at https://savannah.gnu.org/bugs/?37926. Hi James, thanks, your solution is even better - if we can save a stat, then it's definitely worth it. The

Re: [bug #34976] find: Failed to save working directory in order to [...]: Too many open files

3a645ef225776b77657c9da6dae382b9205d0bd0 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker m...@bernhard-voelker.de Date: Mon, 7 Jan 2013 19:22:06 +0100 Subject: [PATCH] find: fix fd leak with --execdir option (bug#34976) Prevent Failed to save working dir[...]: Too many open files error by closing the directories file

[bug #34976] find: Failed to save working directory in order to [...]: Too many open files

Follow-up Comment #5, bug #34976 (project findutils): Patch sent to the ML: http://lists.gnu.org/archive/html/bug-findutils/2013-01/msg2.html ___ Reply to this item at: http://savannah.gnu.org/bugs/?34976

Re: PATCH: simplify printing of time stamps

On 01/05/2013 02:07 AM, Urs Thuermann wrote: This patch simplifies considerably the functions do_time_format() and format_date() used for %A, %C, and %T in the -printf predicate. [...] diff -rup findutils-4.4.2.orig/find/pred.c findutils-4.4.2/find/pred.c ---

Re: Hi small improvement to find command.

On 01/29/2013 07:02 AM, Prashant Sharma wrote: I was curious about the communities interest in a small improvement to mtime's precision from days to seconds, hours and minutes. something like find . -type f -mtime +1m would give me files modified in last one minute. Thanks for the

Re: Small improvement to find's mtime to support for seconds

On 01/29/2013 09:32 AM, Prashant Sharma wrote: On Tue, Jan 29, 2013 at 1:54 PM, Prashant Sharma scrapco...@gmail.comwrote: The need for this arose with following scenario. I have stream processing engine doing some random stuff and creating a lot of files in the process. And since I did not

Re: [bug #34976] find: Failed to save working directory in order to [...]: Too many open files

On 01/07/2013 07:27 PM, Bernhard Voelker wrote: On 01/07/2013 05:20 PM, Aaron Burgemeister wrote: http://savannah.gnu.org/bugs/?34976 The following fixes the issue. Unfortunately, the test-suite is not very comprehensive, so I can't tell 100% if it is free of side effects. Comments

[bug #34976] find: Failed to save working directory in order to [...]: Too many open files

Follow-up Comment #6, bug #34976 (project findutils): Patch amended with a test case: http://lists.gnu.org/archive/html/bug-findutils/2013-02/msg00016.html ___ Reply to this item at: http://savannah.gnu.org/bugs/?34976

Re: [PATCH 2/3] Avoid using 'INCLUDES =' in automake templates.

On 02/04/2013 12:23 AM, James Youngman wrote: Applied, thanks. It seems that only the Changelog entry made it into Git, but the change in import-gnulib.sh did not: http://git.sv.gnu.org/cgit/findutils.git/commit/?id=e1afb49b Have a nice day, Berny

Re: please cut up help text of xargs into manageable translatable chunks

\ ), _(\ ... With other styles, the interjacent fputs(..., stream) calls would make reading and a proper columnar layout harder. Afterward, a simple loop prints out the array. WDYT? Have a nice day, Berny From 532889fa085353875cd4a747f35ab9c8e8d559ac Mon Sep 17 00:00:00 2001 From: Bernhard

[bug #38356] xargs -P option creates wrong result

Additional Item Attachment, bug #38356 (project findutils): File name: xargs-man-mangled-stdout.patch Size:1 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?38356 ___ Message

Re: please cut up help text of xargs into manageable translatable chunks

Hi Benno, sorry for the late reply, but Jay was still waiting for my signed papers anyway (I hope it's done now). On 02/10/2013 10:01 PM, Benno Schulenberg wrote: On Fri, Feb 8, 2013, at 23:01, Bernhard Voelker wrote: Here's the fix. Looks good, except... I don't like the misalignment

Re: please cut up help text of xargs into manageable translatable chunks

ed9284f43e1a8ea1821d3abbad43d7c32e631d9f Mon Sep 17 00:00:00 2001 From: Bernhard Voelker m...@bernhard-voelker.de Date: Tue, 26 Feb 2013 09:14:09 +0100 Subject: [PATCH] xargs: split usage text to help translators Smaller chunks are easier to handle for translators, ideally one msgid per option

[bug #38696] -exec didn't print error message if no '; ' delimiter found and redirection used

Follow-up Comment #1, bug #38696 (project findutils): That is not a bug in find, but rather a misunderstanding on your side of how the shell handles redirections, e.g. man bash, section REDIRECTION: The following redirection operators may precede or appear anywhere within a simple

Re: mnemonic for %* of -printf

On May 15, 2013 at 6:09 PM Peng Yu pengyu...@gmail.com wrote: I find that things like '%H' of -printf is very hard to remember. Is there an easy way to remember '%*'? The are many formats the -printf option supports. What's wrong with looking it up in the man page? Have a nice day, Berny

Re: find -links n

On 07/14/2013 12:19 PM, Günter Wallnig wrote: I believe to have found a mistake in find with the param -links: Apparently, only the second Column of the output of ls looks at what is probably wrong with a directory! If I understand correct, then you are saying that the second column of the

Re: xargs -p operations out of order!

Hi Eric, On 07/31/2013 07:10 PM, Eric Blake wrote: On 07/31/2013 11:01 AM, jida...@jidanni.org wrote: $ seq 111|xargs -n 5 -p Sorry, but this is not xargs' fault. You asked xargs to spawn multiple processed in parallel, [...] I'm not sure: the OP used lower-case -p, so xargs is spawning

Re: [bug #34976] find: Failed to save working directory in order to [...]: Too many open files

On 02/03/2013 08:27 PM, Bernhard Voelker wrote: Hi James, I rebased my previous version of the patch against git HEAD, and simplified a function in the test; see attached. Have a nice day, Berny From 8e239cf781baa4d0e42457ff4737b4518db229cb Mon Sep 17 00:00:00 2001 From: Bernhard Voelker m

[PATCH] maint: avoid overflow warning in xargs

xargs.c: In function 'xargs_do_exec': xargs.c:1274:2: warning: overflow in implicit constant conversion [-Woverflow] * xargs/xargs.c (xargs_do_exec): s/ int r;/ size_t r;/ The gnulib function safe_read returns size_t. --- xargs/xargs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[bug #34976] find: Failed to save working directory in order to [...]: Too many open files

Additional Item Attachment, bug #34976 (project findutils): File name: bug34976.execdir-v3.patch Size:8 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?34976 ___ Message

[bug #34976] find: Failed to save working directory in order to [...]: Too many open files

Follow-up Comment #7, bug #34976 (project findutils): Rebased and amended patch sent to ML (version 3): http://lists.gnu.org/archive/html/bug-findutils/2013-08/msg2.html ___ Reply to this item at: http://savannah.gnu.org/bugs/?34976

[bug #26885] -size checks filesize, not blocks-used-in-filesystem.

Follow-up Comment #7, bug #26885 (project findutils): BTW: In the meantime, du(1) has learned the --threshold option which can be used to filter by file size or by the apparent file size (available in coreutils = v8.21). Git commit: http://git.sv.gnu.org/cgit/coreutils.git/commit/?id=f8afbb42

Re: Is there a memory leak in find ?

On 04/11/2014 06:28 AM, Paul E Condon wrote: I've done more testing using several different trees as input data. In all cases the script terminates well before it has completely walked the tree, always when the output file has grown to about 2.8GB. The last line is always a complete well

Re: Is there a memory leak in find ?

On 04/11/2014 08:30 AM, Bernhard Voelker wrote: Which version of 'find' are you using? I don't see this mem-leaking effect - neither with latest 'find' from the git repository nor with that on my openSUSE-13.1 system (4.5.12). Maximum resident set size (kbytes): 11040 Ha! I could

Re: output as found

On 06/11/2014 04:45 PM, Istvan Toth wrote: is there a way to list files immediately as 'find' finds them? The problem is when searching in large NFS-mounted directories (e.g. millions of files in a poorly designed, flat directory) we must wait for the big number of getdents64 calls to end up

Re: find -limit 44

On 07/30/2014 05:46 AM, 積丹尼 Dan Jacobson wrote: Perhaps a -limit option could be added to find. Would find -limit 22 be much more efficient than find|sed 22q ? Thanks for the proposal, but could you please elaborate in what combination of other flags this might be most useful? I'm asking

Re: info locate has repeated paragraph

On 08/10/2014 05:29 AM, 積丹尼 Dan Jacobson wrote: Repeated paragraph spotted: That's a trivial one, thanks! Have a nice day, Berny From c97c85bfea61dadc478d5959314b26766a546d10 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker m...@bernhard-voelker.de Date: Sun, 10 Aug 2014 10:37:30 +0200 Subject

[bug #42937] xargs --show-limits environment size subtracted twice possibly

Follow-up Comment #1, bug #42937 (project findutils): This seems correct to me, however, then also the output for POSIX upper limit on argument length (this system) should be fixed, too, because that should reflect the original limit without 'size_of_environment' already being subtracted. This

Re: info locate has repeated paragraph

On 08/19/2014 09:25 AM, James Youngman wrote: Bernhard, Thanks for the patch. I added a ChangeLog entry (which findutils still maintains manually[*]), applied and pushed it as 68e2b1d6fd420787903142c02ce1a5e3ea2a7754. Thanks again for your contributions to findutils. thanks, I forgot

Re: info locate has repeated paragraph

On 08/23/2014 01:07 PM, James Youngman wrote: I don't think we should worry about correcting git log entries prior to 2009 when generating ChangeLog. For your (I hope) convenience I just pushed a change which splits the 1987-2008 ChangeLog entries out into a separate file, ChangeLog-2008.

Re: info locate has repeated paragraph

On 08/25/2014 01:44 PM, James Youngman wrote: Thanks for this, it's great. I made a small tweak to your patch in order to support VPATH builds (i.e. where the directory in which configure was run is not $(top_srcdir)). I attach the updated version. I'm running some final checks now, and

[bug #43761] --verbose option is not supported by 'locate'

Follow-up Comment #1, bug #43761 (project findutils): While it's true that findutils' locate(1) doesn't support the --verbose flag, adding this option wouldn't help: $ locate --version mlocate 0.26 You are using one of the distributions which has chosen to replace GNU findutils'

Re: -exec test (use which to only find test once)

On 03/25/2015 11:39 PM, Peng Yu wrote: I find that -exec test ... can be slower than -exec $(which test) Is possible that `find` internally use which, so that users don't need to explicitly call it? Thanks. How much slower is it for you? In my test case, the findutils repository which

Re: How test for directory with single quote (') in the name (with find)?

On 03/04/2015 11:17 PM, Morgan Weetman wrote: The example below has assumed that you wanted to test that .export was a file: find . -type d -exec sh -c test -f \{}\/.export \; -print .. works for me on 4.5.11 Well, the problem is when now a directory has a double quote '' in its name: $

Re: How test for directory with single quote (') in the name (with find)?

On 03/05/2015 12:08 AM, Morgan Weetman wrote: The best I could think of is to avoid the extra shell, and to directly invoke /usr/bin/test instead: $ find . -type d -exec test -f '{}'/.export \; -print This will work for both, directory names with '' and with '\'' in their names. My

Re: -exec test (use which to only find test once)

On 03/26/2015 01:40 AM, Peng Yu wrote: For my case, it is about 10% time difference. This is quite much - well, a real program other than test would probably do much more processing and therefore making the overhead for searching the executable in PATH make smaller in percentage. How does your

Re: Faster way to prune directory?

On 04/16/2015 06:04 AM, Peng Yu wrote: Hi, The following code shows that -prune when used with -exec can be very slow. Is there somehow a way to speed this up? ~$ cat main.sh #!/usr/bin/env bash tmpdir=$(mktemp -d) function mkalotdir { local n=$1 local i local j local k for i in

Re: Faster way to prune directory?

On 04/16/2015 04:51 PM, Peng Yu wrote: real0m0.340s real 0m2.455s Oops, I misread the numbers in your first mail. On my home machine, the example with /usr/bin/test just takes about half a second while it takes ~5 seconds on your host. I now checked on a different system, and it took

[bug #45780] inode column is badly aligned when running 'find dir -ls'

Follow-up Comment #1, bug #45780 (project findutils): Thanks for the report. However, your example output seems to be mangled: as find(1) is using %6s for the inode numbers, you cannot get a smaller inode column than 6 characters. $ find/find /home /var /dev /media -maxdepth 0 -ls 24

[bug #45483] find -atime n Manpage Not Correct

Additional Item Attachment, bug #45483 (project findutils): File name: 0001-doc-fix-example-in-atime-rounding-description.patch Size:0 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?45483

Re: Help needed

On 09/08/2015 01:18 PM, Carlos Lopes wrote: Hi, I'm trying to use findutils to find files based on their name, but since there are many patterns to search, I would like to know if it is possible to pass a file with the patterns: Ex: This works fine: find w:\ -iname "*33*" (it returns a list

Re: "find" ends with exit code "0" although exec command returned an error

On 10/04/2015 06:46 PM, Thomas D. wrote: > Hi, > > for me it looks like "find" returns an invalid exit code when "-exec" > returns an error: > > $ mkdir /tmp/find-test > $ touch /tmp/find-test/scripts{1..10}.sh > $ touch /tmp/find-test/text{1..10}.txt > $ find /tmp/find-test -name '*.sh' -exec

Re: RFE: head,tail: -z, --zero-terminated

Adding . On 09/26/2015 04:43 PM, Richard Russon wrote: > I'd like to add an option to both head and tail, > to allow them to work with NUL-terminated lines of text > -z, --zero-terminated > > Thus allowing: > > find dir -type f -print0 | head -z -n 10 | xargs -0

[PATCH 5/8] maint: adjust some copyright headers manually

This is the prerequesite that 'make update-copyright' will correctly work on these files in future. * configure.ac: Add copyright header, using data from the oldest log entry of this file. * lib/regexprops.c (copying): Adjust copyright year to let 'check-regexprops' pass. * po/fi.po (header

[PATCH 2/8] maint: remove po/Makevars as it is created during bootstrap

* po/Makevars: Remove. This also avoids an sc_trailing_blank failure due to a blank character after the empty EXTRA_LOCALE_CATEGORIES. --- po/Makevars | 88 - 1 file changed, 88 deletions(-) delete mode 100644 po/Makevars diff --git

[PATCH 1/8] build: avoid bootstrap error on clean tree

Avoid the following error when running ./bootstrap on a clean tree: autoreconf: running: aclocal -I gl/m4 --force -I gl/m4 -I m4 configure.ac:129: error: AC_PROG_CC cannot be called after AM_PROG_CC_C_O ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...

[PATCH 7/8] doc: fix typo in find.1

* find/find.1 (GLOBAL OPTIONS): s/occurr/occur/ --- find/find.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/find/find.1 b/find/find.1 index 2f2c974..7166ddd 100644 --- a/find/find.1 +++ b/find/find.1 @@ -442,7 +442,7 @@ and .SS GLOBAL OPTIONS Global options always

[PATCH 0/8] maintenance patches

The following is a list of minor maintenance patches: [PATCH 1/8] build: avoid bootstrap error on clean tree [PATCH 2/8] maint: remove po/Makevars as it is created during bootstrap [PATCH 3/8] maint: update .gitignore files, remove obsolete .cvsignore files [PATCH 4/8] maint: update all

[PATCH 8/8] maint: don't use obsolete gnulib modules

Avoid bootstrap warnings: Notice from module malloc: This module is deprecated. Use the module 'malloc-gnu' instead. Notice from module realloc: This module is deprecated. Use the module 'realloc-gnu' instead. * bootstrap.conf (gnulib_modules): Use malloc-gnu and realloc-gnu modules,

[PATCH 6/8] maint: fix file name in message of findutils-check-pofiles

* Makefile.am (findutils-check-pofiles): s/configure\.in/configure.ac/, as that file has been renamed long ago (FINDUTILS_4_3_8-1-50-gc4ef190). While at it, re-indent the lines to shorten the lines for readability. (coverage-clean): Re-indent likewise. (gen-ChangeLog): While at it, replace leading

[PATCH 4/8] maint: update all copyright year number ranges

* ChangeLog-2013: Change copyright year by 'make update-copyright'. * NEWS: Likewise. * README-hacking: Likewise. * bootstrap: Likewise. * bootstrap.conf: Likewise. * build-aux/Makefile.am: Likewise. * build-aux/check-testfiles.sh: Likewise. * build-aux/gen-changelog.sh: Likewise. *

Re: [PATCH 0/8] maintenance patches

ing: copyright statement not found Thanks & have a nice day, Berny >From 4e884455aefe6636417b1132de02da4365520fb2 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker <m...@bernhard-voelker.de> Date: Mon, 4 Jan 2016 01:08:29 +0100 Subject: [PATCH] maint: adjust some copyright headers manually MI

[PATCH 0/2] further copyright update tweaks

While the 1st patch makes sense to prevent possible problems with the exemption list for 'make update-copyright', the second is a proposal to shorten the copyright headers which are becoming longer and longer over the years. [PATCH 1/2] maint: clarify that .x-update-copyright entries are EREs

[PATCH 1/2] maint: clarify that .x-update-copyright entries are EREs

The entries in the exemption list are processed by "grep -vEf ./.x-update-copyright" and therefore evaluated as an extended regular expression (ERE). Thus, e,g, a "bootstrap" entry would also match for "bootstrap.conf" which we may want to be updated. The current entries are unambiguous so far,

[PATCH 2/2] maint: make copyright statements more consistent

Instead of growing lists of copyright year numbers with gaps, convert the sequence to a minimal containing range, e.g.: -Copyright @copyright{} 1994, 1996, 1998, 2000-2001, 2003-2016 Free -Software Foundation, Inc. +Copyright @copyright{} 1994-2016 Free Software Foundation, Inc. This

Re: [PATCH 0/8] maintenance patches

effect, "make update-copyright" wouldn't have to be tamed to spare these files. Have a nice day, Berny >From 7329171ea9d379b82fd61586a709186cf078a1c3 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker <m...@bernhard-voelker.de> Date: Tue, 5 Jan 2016 00:19:56 +0100 Subj

Re: [Findutils-patches] [PATCH 2/2] maint: make copyright statements more consistent

On 01/05/2016 06:10 PM, James Youngman wrote: > Other than this, the change seems good to me with > UPDATE_COPYRIGHT_USE_INTERVALS=1. Thanks, pushed with that change. Have a nice day, Berny

Re: stable branches (was Re: [PATCH 0/8] maintenance patches)

On 01/05/2016 02:31 PM, Kamil Dudka wrote: Fedora and RHEL maintainers backport mainly fixes for bugs that are reported via Red Hat Bugzilla. At the same time, we update to the latest upstream release in the development version of Fedora, from which the stable Fedora releases are branched each

Re: Historic and proposed future use of branches in the findutils repository

On 01/06/2016 10:20 PM, Assaf Gordon wrote: > I believe "git gc" runs on all git repositories on savannah on the 4th of > every month. good to know, thanks! Have a nice day, Berny

[PATCH 0/3] doc: imp[rove README-hacking

rom 502ace22e9af0c16020b2494af466cd83a40a92c Mon Sep 17 00:00:00 2001 From: Bernhard Voelker <m...@bernhard-voelker.de> Date: Wed, 30 Dec 2015 13:14:57 +0100 Subject: [PATCH 1/3] doc: fix typos in README-hacking * README-hacking (Required format for check-in messages): s/maded/made/; s/modifies

Re: [PATCH] updatedb: run in the C locale, don't do case-folding.

On 01/09/2016 10:18 PM, James Youngman wrote: > * locate/updatedb.sh: Set LC_ALL to C to avoid unexpected character > encodings in path names causing sort to fail (idea from Clarence > Risher). Don't do case-folding, since the character set in now C, > which is likely inconsistent with the user's

Re: Historic and proposed future use of branches in the findutils repository

On 01/05/2016 11:25 PM, James Youngman wrote: > 2) Proposed arrangement for the future > > a) Future of "master": continue to use it for development, but also > cut "stable" releases directly from here. Abandon the use of > "stable" branches. Instead, develop on master and cut stable releases

[patch] maint: avoid syntax-check failures

00 2001 From: Bernhard Voelker <m...@bernhard-voelker.de> Date: Sun, 27 Dec 2015 22:57:47 +0100 Subject: [PATCH 01/10] maint: avoid syntax-check failures * Makefile.am (gen-ChangeLog): Replace 8 spaces by a tab to avoid sc_makefile_TAB_only_indentation failure. --- Makefile.am | 2 +- 1 fi

[bug #19349] doc bug on -size

Follow-up Comment #4, bug #19349 (project findutils): It's already there, both in --help output ... $ find --help | grep ^tests tests (N can be +N or -N or N): -amin N -anewer FILE -atime N -cmin N ... and in the man page: Numeric arguments can be specified as +n for greater

Re: [bug #48180] find -noop segfaults

ice day, Berny >From 595060f28eb5f658fa8d98970959c617fab0f078 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker <m...@bernhard-voelker.de> Date: Tue, 14 Jun 2016 20:49:42 +0200 Subject: [PATCH] Fix bug #48180: find: avoid segfault for internal '-noop' option The pseudo-option '-noop' was never meant to be

[bug #48030] -exec + does not pass all arguments for certain specific filename lengths

Follow-up Comment #6, bug #48030 (project findutils): Please review the attached patch. ___ Reply to this item at: ___ Message sent via/by Savannah

Re: [patch] implicit declaration of function 'explain_how_to_report_bugs'

On 05/28/2016 02:49 PM, Andreas Metzler wrote: > Hello, > > find attached a trivial patch for an implicit function declaration. > > cu Andreas Thanks for the patch. Pushed with minor commit message tweaks as 9cb4175. Have a nice day, Berny

[bug #48030] -exec + does not pass all arguments for certain specific filename lengths

Update of bug #48030 (project findutils): Summary: -exec + does not pass all arguments for ceratin specific filename lengths => -exec + does not pass all arguments for certain specific filename lengths ___ Additional Item

Re: [bug #46815] problem when testing file size

On 01/09/2016 04:41 PM, James Youngman wrote: > Let's re-open the discussion about what to call the "sane" alternative to > -size, and implement it this time. I'm not so enthusiastic, i.e., only 20:80 for adding such a -filesize option. The question is: what functionality would it provide which

Re: [bug #46815] problem when testing file size

On 01/11/2016 12:43 AM, Assaf Gordon wrote: >> Suppose someone wants to find files smaller than 20MiB. Are you sure >> that the best answer we should give them is that they should use >> "find -size -20971520c"? Although this is inconvenient, there are several ways for the user to avoid doing

Re: [Findutils-patches] Rebased extended attribute (-xattr) and capabilty (-cap) patch for find

On 01/16/2016 07:21 AM, Morgan Weetman wrote: Hi all, Resubmitting this patch for review, allows finding files based on extended attributes or capabilities, any feedback would be appreciated It'd be good to have XATTR/CAP support (de-)configurable rather than adding hard dependencies. Have a

Re: [bug #48180] find -noop segfaults

On 06/14/2016 08:58 PM, Bernhard Voelker wrote: > On 06/08/2016 06:35 PM, anonymous wrote: >> URL: >> <http://savannah.gnu.org/bugs/?48180> > ... >> >> $ find -noop >> [1]4043 segmentation fault (core dumped) find -noop > > Thanks for the rep

Re: [PATCH] xargs: better error message for xargs -s notanumber.

On 01/25/2016 12:45 AM, James Youngman wrote: > On Sun, Jan 24, 2016 at 10:19 PM, Bernhard Voelker > <m...@bernhard-voelker.de> wrote: >> What about something like the following - shorter ? >> >> $ xargs/xargs -s ABC >> xargs/xargs: invalid number "

Re: [PATCH] xargs: better error message for xargs -s notanumber.

ng - shorter ? $ xargs/xargs -s ABC xargs/xargs: invalid number "ABC" for -s option Try 'xargs/xargs --help' for more information. The attached patch is a draft to do this (on top of your patch). Have a nice day, Berny >From 033b2dfb9eb12cd1d4d02953d5ed33d4a449521e Mon Sep 17 00:00:00 2001 F

[PATCH 4/6] all: output full usage only when requested via the --help option

When there are invalid options or arguments, all utilities printed the full usage in addition to the original error diagnostic. The quite large text distracted the user's attention from the error message. * find/defs.h (usage): Mark as _GL_ATTRIBUTE_NORETURN, and remove the arguments FP and MSG.

[PATCH 1/6] maint: avoid syntax-check failures

'make syntax-check' failed with: locate/word_io.h: maint.mk: the above files include assert.h but don't use it maint.mk:479: recipe for target 'sc_prohibit_assert_without_use' failed ... lib/bugreports.h: maint.mk: empty line(s) or no newline at EOF maint.mk:929: recipe for target

[PATCH 5/6] doc: improve description of the -D option in find.1

* find/find.1 (-D): Change argument name from "debugoptions" to "debugopts" to match the synopsis, thus making searching in the man page easier. While at it, sort possible arguments alphabetically. --- find/find.1 | 24 ++-- 1 file changed, 14 insertions(+), 10 deletions(-)

[PATCH 3/6] maint: adjust .gitignore files

* lib/.gitignore: Use pattern for prominent suffixes like *.o, *.log and *.a; an entry for the new intermediate file bugreports.o was missing here. Sort file. * locate/.gitignore (bigram,code,bigram.o,code.o): Remove, as these programs have been removed with commit v4.6.0-44-g89ec021. *

[PATCH 2/6] maint: add new bugreports.c to POTFILES.in

* po/POTFILES.in (lib/bugreports.c): Add entry. --- po/POTFILES.in | 1 + 1 file changed, 1 insertion(+) diff --git a/po/POTFILES.in b/po/POTFILES.in index f6b7aed..f40778c 100644 --- a/po/POTFILES.in +++ b/po/POTFILES.in @@ -16,6 +16,7 @@ find/pred.c find/print.c find/tree.c find/util.c

Re: [Findutils-patches] [PATCH 0/6]: usage change et al

On 02/22/2016 12:20 AM, James Youngman wrote: > Thanks for working on these; please apply them. Thanks for the review; pushed. Have a nice day, Berny

Re: Patches to -type x,y,z

On 04/06/2016 06:14 PM, Dale R. Worley wrote: > Bernhard Voelker <m...@bernhard-voelker.de> writes: >> I thought a bit about the implementation and thought it'd be better >> to avoid artificially creating the OR-ed predicates, and rather store >> the wanted file

Re: xargs --negate-interactive

On 04/10/2016 03:52 PM, 積丹尼 Dan Jacobson wrote: > BV> Without RET, this would all be mangled and the commands would be > BV> unreadable on a terminal. > > All I know is there could be an additional option added to switch it > into a mutt mail reader like mode just before waiting for each

Re: xargs --negate-interactive

On 04/10/2016 03:12 PM, 積丹尼 Dan Jacobson wrote: > Wait, how about an option to eliminate the need for RET: > > so now all they would need to type is > > RET y RET RET y y > or even > x y x x y y > or any non y ... > wait, how about just n,y,and q(to quit), and maybe "." to

Re: Patches to -type x,y,z

On 04/08/2016 03:15 PM, Young Mo Kang wrote: > On 04/06/2016 07:33 PM, Bernhard Voelker wrote: >> Sorry for the late reply. >> I thought a bit about the implementation and thought it'd be better >> to avoid artificially creating the OR-ed predicates, and rather store >

Re: xargs: Kill children to stop immediately

On 04/01/2016 11:56 AM, Orivej Desh wrote: > I would like xargs to attempt to terminate its children when one of them > returns with the code 255 to stop immediately, whereas currently xargs > imposes unnecessary delay and, when process produce output, makes the > output of a failing process to be

Re: xargs --negate-interactive

On 04/08/2016 03:52 PM, 積丹尼 Dan Jacobson wrote: > xargs has > >-p, --interactive > Prompt the user about whether to run each command line and read > a line from the terminal. Only run the command line if the re- > sponse starts with `y' or `Y'.

[bug #47482] man page example error

Update of bug #47482 (project findutils): Status:None => In Progress ___ Follow-up Comment #1: Thanks for the report. Patch attached - pushing soon. Have a nice day, Berny (file #36720)

[bug #47482] man page example error

Update of bug #47482 (project findutils): Status: In Progress => Fixed Open/Closed:Open => Closed ___ Reply to this item at:

Re: [6 PATCHES] New feature added to find: -type xyz

On 02/28/2016 11:06 PM, Young Mo Kang wrote: > I just thought it would be useful to enable multiple type search at once > feature in find, i.e., find’s option "-type xyz” can be a shorthand form > for “( -type x -o -type -y -o -type z )”. It should work with -xtype exactly > the same way. > > To

[patch #9005] Manual typo fixes

Additional Item Attachment, patch #9005 (project findutils): File name: 0001-doc-fix-spelling-of-output.patch Size:2 KB ___ Reply to this item at: ___

[patch #9005] Manual typo fixes

Update of patch #9005 (project findutils): Status:None => In Progress Assigned to:None => berny ___ Follow-up Comment #1: Thanks for the

Re: xargs --negate-interactive

On 04/10/2016 04:26 PM, 積丹尼 Dan Jacobson wrote: >>>>>> "BV" == Bernhard Voelker <m...@bernhard-voelker.de> writes: > BV> Well, there are many possibilities, but there is already a way to > BV> to do it in xargs. So what would you want to achieve b

Re: [PATCH] clarify exit status handling of -exec command {} +

On 04/18/2016 08:42 AM, Kamil Dudka wrote: Looks good to me. Thank you for polishing the patch! Thanks, pushed. Have a nice day, Berny

Re: xargs --negate-interactive

On 07/16/2016 04:17 PM, James Youngman wrote: > I quite like the idea. Here's an example implementation of a flag that > could be used in a shell function/alias, if that's your thing. Comments? > > 0001-xargs-add-new-option-interactive-default-yes-modifyi.patch > > > From

  1   2   3   4   5   6   7   8   >