[bug #67330] -exec[dir] has odd behavior when there are a lot of files

Update of bug #67330 (group findutils): Open/Closed:Open => Closed ___ Follow-up Comment #4: For further clarification, eventually the following example helps. mkdir test cd test # Test 1: first traverse '

[bug #67330] -exec[dir] has odd behavior when there are a lot of files

Update of bug #67330 (group findutils): Status:None => Invalid Assigned to:None => berny ___ Follow-up Comment #3: yes, the find command issued is the problem, because

Re: regexprops-generic propagation

On 7/10/25 07:56, Bruno Haible wrote: Bernhard Voelker wrote: * [PATCH 2/3] regexprops: sort regex_map alphabetically https://cgit.git.sv.gnu.org/cgit/findutils.git/commit/?id=c9c2c511759 * [PATCH 3/3] doc: regenerate regexprops.texi https://cgit.git.sv.gnu.org/cgit/findutils.git

Re: [PATCH] Update RE_SYNTAX_EMACS to include features used by GNU Emacs

On 7/10/25 02:38, Collin Funk wrote: Bernhard Voelker writes: 2. Commit (to be pushed) to gnulib - see attachment. Good to push? That patch looks good, thanks. I confirmed that I receive the same output when running './regexprops "Regular Expressions" generic'. T

Re: [PATCH] Update RE_SYNTAX_EMACS to include features used by GNU Emacs

cgit/findutils.git/commit/?id=facc27e1804 2. Commit (to be pushed) to gnulib - see attachment. Good to push? Have a nice day, Berny From f3aaeaf5e2d1cbbbd8c90c4389e7204aa079fdcb Mon Sep 17 00:00:00 2001 From: Bernhard Voelker Date: Wed, 9 Jul 2025 21:06:12 +0200 Subject: [PATCH] regexprops-ge

Re: Error report: There is an error in the manual of findutilis

On 7/7/25 10:46, zhaiyn wrote: Because I do not have the ability to write in English, the following content is in Chinese. Sorry! 出现错误的内容链接: https://www.gnu.org/software/findutils/manual/html_node/find_html/Finding-the-Shallowest-Instance.html ; 在该文中，示例代码是这样写的:   find repo/ \   -exec test -

[bug #67220] Feature request: Add 'mnewer' as an alias of 'newer'

Update of bug #67220 (group findutils): Status:None => Fixed Assigned to:None => berny Fixed Release:None => 4.11.0 ___ Follow-up Comment

Re: [PATCH] find: add option -fail_exec

On 5/21/25 19:24, Tavian Barnes wrote: On Wed, May 21, 2025 at 1:51 AM Bernhard Voelker wrote: [snip] Although I like in general the idea to have more control over exit values in the caller, I have the suspicion that mapping to EXIT_FAILURE may be too simple: How to distinguish that from

Re: [PATCH] find: add option -fail_exec

On 5/20/25 22:56, Bernhard Voelker wrote: > So would you please describe further your use cases with some > examples? P.S. It makes sense looking over the fence as well: does one of the other find(1) implementations have such a feature already, and how is it solved there? Thanks & h

Re: [PATCH] find: add option -fail_exec

On 5/3/25 17:07, Tomas Mudrunka wrote: When find -exec is used in build scripts, ci pipelines and similar, it's good to have way to ensure that failed subprocess executed by find results in non zero return code of find as whole. Thanks for the suggestion and the patch. Previously this was onl

[bug #62259] find(1) manpage prune example error

Update of bug #62259 (group findutils): Status: In Progress => Fixed ___ Follow-up Comment #8: Fair enough - pushed: - doc: supplement list of actions that suppress default -print https://git.sv.gnu.org/cgit

Re: [PATCH] doc: Add missing actions from list that suppress default

On 4/25/22 05:39, raf wrote: Hi, find/find.1 and doc/find.texi contain a list of the actions that suppress the default -print action. But -print0 and -fprint0 are missing from the list. This patch adds them to the list in both files. Thanks - phew, time flies! Meanwhile, the translators have s

[bug #62259] find(1) manpage prune example error

Update of bug #62259 (group findutils): Status:None => In Progress Assigned to:None => berny ___ Follow-up Comment #6: Alright, let's fix the errors - done with the 3 a

[bug #66965] Multiple -files0-from args overwrite each other

Update of bug #66965 (group findutils): Fixed Release:None => 4.11.0 ___ Follow-up Comment #2: Pushed a test to document the behavior: https://git.sv.gnu.org/cgit/findutils.git/commit/?id=ee500667d499 _

Re: Are these system crashes fixed in the latest version?

n error. Fair enough. As accepting '-!' is a GNU extension (even if probably inadvertently), I think we can safely issue a warning without setting the error status. Patch attached. Pushing soon. Have a nice day, Berny From f1fa80330bb57353c99884affa5e372824f75056 Mon Sep 17 00:00:00 20

[bug #66965] Multiple -files0-from args overwrite each other

Update of bug #66965 (group findutils): Status:None => Working as Intended Assigned to:None => berny ___ Follow-up Comment #1: Thanks for the report. However, it is qui

Re: find.1: Some remarks and a patch with editorial changes for this man page

Hi Bjarni, On 3/8/25 16:50, Bjarni Ingi Gislason wrote: * What led up to the situation? Checking for defects with a new version test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man page" [Use "groff -e ' $' -e '\\~$' " to find obvious trailing spaces.]

[PATCH] maint: remove declared-only find_pred_name

Only user was inside a an #ifdef DEBUG / #endif block. Introduced with -context in commit v4.5.5-42-g1a05af6a. * find/parser.c (parse_context): Remove #ifdef/#endif block. * find/defs.h (find_pred_name): Remove declaration. --- find/defs.h | 5 - find/parser.c | 3 --- 2 files changed, 8 de

Re: Are these system crashes fixed in the latest version?

On 3/23/25 23:45, Bernhard Voelker wrote: > Pushing soon. Pushed at: https://git.savannah.gnu.org/cgit/findutils.git/commit/?id=dc3365628e24c Have a nice day, Berny

Re: Are these system crashes fixed in the latest version?

On 3/14/25 22:45, raf wrote: On Fri, Mar 14, 2025 at 09:11:01AM +0100, Bernhard Voelker wrote: What worries me more is the use of the extra dash '-' for the logical elements '-)' and '-!'. What exactly needs to be fixed? Find should not allow things l

Re: Are these system crashes fixed in the latest version?

On 3/13/25 18:45, Bernhard Voelker wrote: $ find "-)" "," "-!" "-ls" find: invalid expression: expected expression before closing parentheses '-)'. This one seems to have been fixed with this commit: https://git.savannah.gnu.org/cgit/findu

Re: Are these system crashes fixed in the latest version?

On 3/13/25 05:46, 김민종 wrote: Hi, I'm using findutils-4.7.0 in Ubuntu. While using this program, I found that certain CLI commands caused the system to crash, as shown below: $./find "-)" "," "-!" "-ls" Segmentation fault $ find --version | sed 1q find (GNU findutils) 4.10.0+git.42.faa13013 $

Re: Using .ignore file in find

On 2/13/25 09:16, Grigorii Sokolik wrote: Dear findutils maintainers team! In the software development world there is a widespread practice of using ignore files. Examples are: - .gitignore - .dockerignore - .clang-format-ignore - ... All of them have the same syntax and the same log

Re: find terminated with SIGSEGV in partial_quotearg_n

On 2/7/25 08:29, Dietmar Hahn (Fujitsu) wrote: From: Bernhard Voelker , sent: Sunday, January 26, 2025 6:26 PM https://git.sv.gnu.org/cgit/findutils.git/commit/?id=e5d6eb919b9 I couldn't reproduce the issue here, so maybe you could check? Yes, but couldn't reproduce. no worr

[bug #45930] -ignore_readdir_race ineffective in find 4.5.11 and 4.5.14

Follow-up Comment #18, bug #45930 (group findutils): This issue is not because of the directory type, but ...ugh, rather because the -execdir action resets ignore_readdir_race=false: https://git.savannah.gnu.org/cgit/findutils.git/tree/find/parser.c?id=faa13013686b17#n2812 You can verify by addi

Re: find terminated with SIGSEGV in partial_quotearg_n

On 1/26/25 9:29 PM, James Youngman wrote: error (0, 0, _("File system loop detected; " "the following directory is part of the cycle: %s"), safely_quote_err_filename (0, ent->fts_path)); Would it be clearer to stick to just saying "cycle" or "loop" but not using both words? I'm just

Re: tests: adjust shell syntax that breaks AIX /bin/sh

On 1/26/25 07:29, Collin Funk wrote: On AIX, /bin/sh causes a testsuite failure with an output like this: Running /home/collinfunk/findutils-4.10.0.40-d4417/find/testsuite/find.gnu/execdir-multiple.exp ... FAIL: execdir-multiple.new-O0, ./runme[6]: syntax error at line 7 : `newline

Re: find terminated with SIGSEGV in partial_quotearg_n

On 1/24/25 16:03, Dietmar Hahn (Fujitsu) via Bug reports for the GNU find utilities wrote: From: Bernhard Voelker The fts_cycle looks corrupted. The underlying gnulib code seems to be a bit vague about this, and the comment about coreutils is also not true (any more): https

Re: find terminated with SIGSEGV in partial_quotearg_n

Hi Dietmar, On 1/22/25 15:47, Dietmar Hahn (Fujitsu) via Bug reports for the GNU find utilities wrote: Hi list, I have 2 core files from the find command. It's findutils-4.8.0-1.20 from SuSE SLES15SP5. thanks for the bug report. Core was generated by `find -type f -name *xx* -empty -delete

[bug #46791] wishlist: no option to find devices for major/minor

Update of bug #46791 (group findutils): Status:Obsolete => None Assigned to: jay => berny Open/Closed: Closed => Open ___ Follow-up Comment #5:

[PATCH] pred.c: consolidate numerical comparisons

Several predicate tests perform a numerical comparison based on the comparison_type (COMP_GT, COMP_LT, COMP_EQ). Factor that out into a utility function. * find/pred.c (compare_num): Add static function. (pred_gid, pred_inum, pred_links, pred_size, pred_uid): Use it. --- find/pred.c | 117 +++

[bug #66591] default command of xargs in texinfo documentation

Follow-up Comment #2, bug #66591 (group findutils): P.S. The usage output from 'xargs --help' had it wrong; I fixed it (and also added a sentence about the default COMMAND): -Usage: xargs [OPTION]... COMMAND [INITIAL-ARGS]... +Usage: xargs/xargs [OPTION]... [COMMAND [INITIAL-ARGS]...] Pushed at:

[PATCH] xargs: clarify command as optional in --help output

* xargs/xargs.c (usage): Fix synopsis by wrapping COMMAND in '[...]', because it is in fact optional. Also add a sentence that the default COMMAND is 'echo'. --- xargs/xargs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/xargs/xargs.c b/xargs/xargs.c index 8abdd790..517f9

[bug #66591] default command of xargs in texinfo documentation

Update of bug #66591 (group findutils): Category: xargs => documentation Status:None => Fixed Assigned to:None => berny Fixed Release:None => 4.11.0

[PATCH 1/5] maint: update copyright year number ranges

Run 'make update-copyright'. * lib/regexprops.c (copying): Update the year number manually. * tests/sample-test: Adjust to use the single most recent year. * All other files: Update copyright years via the above make run. --- Makefile.am| 2 +- NEWS

[PATCH 5/5] maint: silence GCC-14 on utility source getlimits.c

Seen on GCC 14: getlimits.c:73:3: warning: stack-based buffer overflow [CWE-121] \ [-Wanalyzer-out-of-bounds] 73 | sprintf (limit + 1, "%" "ju", (uintmax_t) TYPE##_MAX); \ | ^ ... while limit is defined more than large

[PATCH 0/5] Year 2025 maint patches incl. gnulib update

This patch series is about some maintenance work for the GNU findutils to start into a hopefully Happy New 2025: * [PATCH 1/5] maint: update copyright year number ranges * [PATCH 2/5] maint: update gnulib to latest * [PATCH 3/5] xargs: simplify error handling for gnulib's safe_read * [PATCH 4/5] m

[PATCH 2/5] maint: update gnulib to latest

Run 'make update-gnulib-to-latest'; there have been 1127 commits on gnulib since the last update. * gnulib: Update to latest. * bootstrap: Likewise. * bootstrap-funclib.sh: Likewise. * cfg.mk (exclude_file_name_regexp--sc_fsf_postal): Add to exempt the script build-aux/src-sniff.py from this synta

[PATCH 4/5] maint: adjust to gnulib module renaming

Since previous gnulib update, './bootstrap' shows deprecation warnings like the following for several modules: Notice from module errno: This module is deprecated. Use the module 'errno-h' instead. Use the newer names instead: - errno -> errno-h - inttypes -> inttypes-h - locale -> locale-h -

[PATCH 3/5] xargs: simplify error handling for gnulib's safe_read function

The gnulib/NEWS file states: SAFE_READ_ERROR and SAFE_WRITE_ERROR are now obsolescent; callers can just check for < 0. * xargs/xargs.c (xargs_do_exec): Adjust error handling of safe_read accordingly. --- xargs/xargs.c | 110 +- 1 file changed, 4

[PATCH] maint: pull in gnulib module basename-lgpl

* bootstrap.conf (gnulib_modules): Add 'basename-lgpl', because we're using the gnulib 'base_name' function. --- bootstrap.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/bootstrap.conf b/bootstrap.conf index bfd84141..2485e2ab 100644 --- a/bootstrap.conf +++ b/bootstrap.conf @@ -76,6 +76

[bug #66568] document whether find's -execdir option is guaranteed to produce pathnames that start with ./

Update of bug #66568 (group findutils): Status: Confirmed => Fixed Fixed Release:None => 4.11.0 ___ Follow-up Comment #3: Thanks - pushed with some minor tweaks, e.g. the commi

[bug #45930] -ignore_readdir_race ineffective in find 4.5.11 and 4.5.14

Follow-up Comment #14, bug #45930 (group findutils): Are you sure? Exactly your test case is now really stable with the patch from comment #11 here. ___ Reply to this item at:

[bug #45930] -ignore_readdir_race ineffective in find 4.5.11 and 4.5.14

Follow-up Comment #11, bug #45930 (group findutils): Alright, that's yet another case than the already-fixed one. The fix for this one would look like the following. diff --git a/find/ftsfind.c b/find/ftsfind.c index 89ed9dd0..f57fa809 100644 --- a/find/ftsfind.c +++ b/find/ftsfind.c @@ -304,6 +3

[bug #66568] document whether find's -execdir option is guaranteed to produce pathnames that start with ./

Update of bug #66568 (group findutils): Category:None => documentation Status:None => Confirmed Assigned to:None => berny ___ Follow-

Re: xargs: doesn't fail on missing terminator (which may have severe consequences)

On 12/15/24 20:47, Bernhard Voelker wrote: `xargs -0` is similar to many tools allowing Zero-delimited input. And often the last entry of input does not have to be Zero-terminated. Here some examples from the GNU coreutils. * `sort -z`: * `uniq -z`: * `cut -z` * `tail -z`: P.S. I forgot to

Re: xargs: doesn't fail on missing terminator (which may have severe consequences)

Hi Chris, On 12/14/24 19:55, Christoph Anton Mitterer wrote: On Fri, 2024-12-13 at 23:05 +0100, Bernhard Voelker wrote: I never saw a practical example why it would be dangerous. Well it seems to me, that in that case even a 1 in Million chance might have too catastrophic consequences to

Re: xargs: doesn't fail on missing terminator (which may have severe consequences)

Hi Christoph, On 12/12/24 4:17 PM, Christoph Anton Mitterer wrote: So I'd still ask you to consider whether GNU's xargs can be modified accordingly (and not just in some POSIXLY_CORRECT mode), as any other behaviour seems truly dangerous to me. I never saw a practical example why it would be d

Re: xargs: doesn't fail on missing terminator (which may have severe consequences)

On 12/9/24 03:34, Christoph Anton Mitterer wrote: Hey. Not sure whether this has been brought up before (at least a quick search didn't reveal anything in the bug tracker or the archive). xargs -0 still executes the command even when no terminating NUL has been found in the (last) line. As sho

Re: maint: don't use gettimeofday

On 8/2/24 06:46, Collin Funk wrote: Patch attached. Thanks, now as the Copyright paperwork is done, I pushed both: * maint: don't use gettimeofday https://git.savannah.gnu.org/cgit/findutils.git/commit/?id=5db475b30607242227571a97355339392274abfc * maint: update Makefile variables used by

[bug #66418] Typo in Leaf Optimisation

Update of bug #66418 (group findutils): Category:find => documentation Status:None => Fixed Assigned to:None => berny Release:None => 4.10.0 Fi

[PATCH 3/4] maint: prefer endian.h for byte order conversions

Now that is a part of POSIX 2024 it should become more portable than . * bootstrap.conf (gnulib_modules): Remove byteswap; add endian. * locate/word_io.c: Include endian.h instead of byteswap.h. (decode_value): Use htobe32 instead of bswap_32. --- bootstrap.conf | 2 +- locate/word_io.c | 4 ++

[PATCH 0/4] some maint patches

* [PATCH 1/4] maint: list Gnulib sys_types directly * [PATCH 2/4] maint: import tests/init.sh from Gnulib during bootstrap * [PATCH 3/4] maint: prefer endian.h for byte order conversions * [PATCH 4/4] maint: remove unused include from fstype.c

[PATCH 2/4] maint: import tests/init.sh from Gnulib during bootstrap

* bootstrap.conf (bootstrap_post_import_hook): Use gnulib-tool --copy-file to import tests/init.sh. * tests/init.sh: Remove file. * tests/.gitignore (/init.sh): Add entry. * Makefile.am (update-gnulib-to-latest): Remove handling tests/init.sh. --- Makefile.am | 4 +- bootstrap.conf | 5

[PATCH 1/4] maint: list Gnulib sys_types directly

* bootstrap.conf (gnulib_modules): Add sys_types. Although it’s already brought in indirectly, findutils code includes directly. --- bootstrap.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/bootstrap.conf b/bootstrap.conf index 39c17e58..cb3fd89b 100644 --- a/bootstrap.conf +++ b/bootst

[PATCH 4/4] maint: remove unused include from fstype.c

With newer gnulib, the sc_prohibit_always_true_header_tests check fails with: find/fstype.c:30:#if HAVE_MNTENT_H maint.mk: do not test the above HAVE__H symbol(s); with the corresponding gnulib module, they are always true make: *** [maint.mk:969: sc_prohibit_always_true_header_tests] Err

Re: [bug #66365] find -exec treats + as special when it shouldn't

57fb016b73c2df6ab5e4cc908f716b520373f53a Mon Sep 17 00:00:00 2001 From: Bernhard Voelker Date: Sun, 3 Nov 2024 21:14:37 +0100 Subject: [PATCH 4/4] maint: add NEWS entry for recent 'find -execdir/-okdir' change * NEWS (Changes in find): Reflect the change in behavir in recent commit v4.10.0-15-g1dcdf3de. ---

Re: [bug #66365] find -exec treats + as special when it shouldn't

Hi James, thanks, technically this patch fixes it, yet I think it deserves some more love before pushing. First of all, this patch does not cleanly apply. $ git am /tmp/x.patch Applying: Fix Savannah bug 66365. error: git diff header lacks filename information when removing 1 leading pa

Re: new module 'hasmntopt'

On 10/7/24 18:58, Bruno Haible wrote: Either remove that #include (since fstype.c does not need it, AFAICS), or make it unconditional. Good point, thanks. Indeed. Thanks for the report. This patch fixes it: Thanks! Have a nice day, Berny

Re: new module 'hasmntopt'

On 8/19/24 5:23 PM, Bruno Haible wrote: 2024-08-19 Bruno Haible ... hasmntopt: New module. ... 2024-08-19 Bruno Haible mntent: New module. While trying to update gnulib in findutils, I've been prompted by this new syntax-check failure: find/fstype.c:30:#if HAVE_M

[PATCH 0/4] maintenance patches

Pushed the following 4 minor maintenance changes: * [PATCH 1/4] maint: pacify GCC 14.2 https://git.sv.gnu.org/cgit/findutils.git/commit/?id=4a719e65d279f81b64a2456b0250cedcb284010a * [PATCH 2/4] maint: adjust to Gnulib -Wsystem-headers change https://git.sv.gnu.org/cgit/findutils.git/commi

[bug #45930] -ignore_readdir_race ineffective in find 4.5.11 and 4.5.14

Update of bug #45930 (group findutils): Status: Code Review => Fixed ___ Follow-up Comment #8: Pushed with a fix for a minor typo in NEWS at: https://git.sv.gnu.org/cgit/findutils.git/commit/

Re: [PATCH] find: add bison as a requirement for compiling

On 9/17/24 04:47, Dave wrote: Thanks for the tweak, lgtm. Thanks, pushed at: https://git.savannah.gnu.org/cgit/findutils.git/commit/?id=07bd7fa675e Have a nice day, Berny

[bug #45930] -ignore_readdir_race ineffective in find 4.5.11 and 4.5.14

Update of bug #45930 (group findutils): Status:None => Code Review Fixed Release:None => 4.11.0 ___ Follow-up Comment #7: I propose to push t

Re: [PATCH] find: add bison as a requirement for compiling

s): Add gnulib variable with tools including bison. Co-authored-by: Bernhard Voelker Copyright-paperwork-exempt: Yes --- README-hacking | 1 + bootstrap.conf | 1 + cfg.mk | 3 +++ 3 files changed, 5 insertions(+) diff --git a/README-hacking b/README-hacking index 0d96dc84..53ae3f2d

Re: Feature Requests for find and date

[moving from coreut...@gnu.org [1] to here] [1] https://lists.gnu.org/r/coreutils/2024-08/msg8.html On 8/19/24 14:10, Pádraig Brady wrote: On 18/08/2024 00:47, Marc Gutt wrote: Dear GNU Team, I like to see the following features / enhancements: find Add %z to help / man page. The numeric

[bug #65998] xargs strange behavior

Follow-up Comment #3, bug #65998 (group findutils): Further hint: one can see what's going on with the '-t,--verbose' option: $ echo '-e test1 -e test2' | xargs -t echo -e test1 -e test2 test1 -e test2 ___ Reply to this item at:

Re: test-framework-sh: Fix typo in function invocation (regression 2024-06-11).

[+findutils ML] Hi Colin, On 6/24/24 9:00 AM, Collin Funk wrote: Hi Bernhard, Bernhard Voelker writes: thanks for the heads-up, but findutils doesn't have 5c2e65d9c760 (June 12), but is on the older commit 623bcc22f474 from (May 27); hence the bug is/was not yet there. :-) Sorr

[PATCH] doc: avoid sc_prohibit_unhyphenated_eof failure

'make syntax-check' complains: maint.mk: use "end-of-file", not "end of file" make: *** [cfg.mk:273: sc_prohibit_unhyphenated_eof] Error 1 * doc/find.texi (xargs options): Change as suggested by the SC rule. --- doc/find.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --g

Re: test-framework-sh: Fix typo in function invocation (regression 2024-06-11).

[FWing to findutils ML] On 6/24/24 2:55 PM, Bernhard Voelker wrote: Hi Collin, On 6/24/24 9:43 AM, Collin Funk wrote: Hi Bernhard, I said: gmake  tests/xargs/test-sigusr gmake[2]: Entering directory '/home/collin/.local/src/findutils'    CC   tests/xargs/test-sigusr.o tests/

Re: findutils 4.9.0: localeconv test failed on RISCV

On 6/6/24 11:01, Yuqi Guo wrote: File:     gnulib-tests/test-localeconv.c Code: ``` struct lconv *l = localeconv (); ASSERT (l->frac_digits == CHAR_MAX); ASSERT (l->p_cs_precedes == CHAR_MAX); ASSERT (l->p_sign_posn == CHAR_MAX); ASSERT (l->p_sep_by_space == CHAR_MAX); ASSERT (l->n_cs_prec

update of the online manual [was: GNU findutils 4.10.0 released]

On 6/1/24 19:03, Bernhard Voelker wrote: > This is to announce findutils-4.10.0, a stable release. P.S. I've pushed the update of the online documentation: https://www.gnu.org/software/findutils/manual/find.html

GNU findutils 4.10.0 released

t the GNU findutils package to the mailing list (<mailto:bug-findutils@gnu.org): https://lists.gnu.org/mailman/listinfo/bug-findutils There have been 88 commits by 8 people in the - sigh - 121 weeks since 4.9.0: Antonio Diaz Diaz (2) James Youngman (24) Bernhard Voelker (57)

Re: [bug #65812] make dist includes bnary file

ts: re-introduce all_tests needed by syntax-check Have a nice day, BernyFrom 3d822be55af9eec550c50e4bca70113dd02e1f82 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker Date: Sat, 1 Jun 2024 16:10:53 +0200 Subject: [PATCH 1/2] maint: improve ERE in sc_tests_list_consistency The ERE used lacks the grouping

[PATCH] maint: add more file related to test-sigusr to tests/.gitignore

* tests/.gitignore (/xargs/.dirstamp): Add entry. (/xargs/test-sigusr.o): Likewise. --- tests/.gitignore | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tests/.gitignore b/tests/.gitignore index 46240f57..58eeacc3 100644 --- a/tests/.gitignore +++ b/tests/.gitignore @@ -1,4 +1,6 @@ /*/*.log

[bug #65282] Positional option -regextype not mentioned

Update of bug #65282 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #52592] Documentation for 'find' unclear on default regex type

Update of bug #52592 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #61304] Contradiction about default type of regular expressions

Update of bug #61304 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #63949] find -inum (without argument) print worng error message

Update of bug #63949 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #65804] ~/bin detected as relative path

Update of bug #65804 (group findutils): Open/Closed:Open => Closed ___ Follow-up Comment #7: This issue is not about a problem or something to improve in find(1), so I'm hereby marking this

[bug #65812] make dist includes bnary file

Update of bug #65812 (group findutils): Open/Closed:Open => Closed ___ Reply to this item at: ___ Mess

[bug #65283] Misleading statement, I believe

Update of bug #65283 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #65378] B or b?

Update of bug #65378 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #64900] Cannot search for files/folders with user/group id bigger than 2147483647

Update of bug #64900 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #64876] Minor typo in updatedb(1) man page

Update of bug #64876 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #64717] find-4.9.0: aborted after assertion at line 3179 of parser.c

Update of bug #64717 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #64480] Docs: Replace examples containing deprecated xargs option "-l" with "-L 1"

Update of bug #64480 (group findutils): Fixed Release:None => 4.10.0 ___ Reply to this item at: ___ Mess

[bug #63934] tests/xargs/verbose-quote.sh fails with dash shell as /bin/sh

Update of bug #63934 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #62325] is This Typo?(xargs.1)

Update of bug #62325 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #62227] Incorrect warning for -name /

Update of bug #62227 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #65804] ~/bin detected as relative path

Update of bug #65804 (group findutils): Status:None => Working as Intended Assigned to:None => berny ___ Follow-up Comment #1: "~" is a meta-chara

[bug #63461] Typo in pt_BR.po

Update of bug #63461 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #65794] Automake warnings for tests/xargs/test-sigusr.c

Update of bug #65794 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #56410] find -L doesn't follow symlinks outside the specified search scope

Update of bug #56410 (group findutils): Fixed Release: 4.7.0 => None ___ Reply to this item at: ___ Mess

[bug #58384] incorect documentaion for -regex

Update of bug #58384 (group findutils): Open/Closed:Open => Closed Release:None => 4.7.0 Fixed Release: 4.7.0 => 4.10.0 _

[bug #58427] Cost-base optimiser breaks short-circuit evaluation

Update of bug #58427 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #51926] -xtype l fails on symbolic links that have a loop

Update of bug #51926 (group findutils): Open/Closed:Open => Closed Release:None => 4.9.0 Fixed Release:None => 4.10.0 _

[bug #63605] Large number of UBSAN failures in test suite

Update of bug #63605 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #64442] xargs closes stdin on receiving SIGUSR1 or SIGUSR2

Update of bug #64442 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #64451] Unexpected behaviour of xargs when multiple children exit with 255 in parallel

Update of bug #64451 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

  1   2   3   4   5   6   7   8   9   >