[bug #62227] Incorrect warning for -name /

2024-06-01 Thread Bernhard Voelker
Update of bug #62227 (group findutils): Open/Closed:Open => Closed Fixed Release:None => 4.10.0 ___ Reply to this item at:

[bug #62227] Incorrect warning for -name /

2022-04-24 Thread Bernhard Voelker
Update of bug #62227 (project findutils): Status: Code Review => Fixed ___ Follow-up Comment #7: Good catch, thanks. Fixed and pushed here: https://git.sv.gnu.org/cgit/findutils.git/commit/?

[bug #62227] Incorrect warning for -name /

2022-04-15 Thread anonymous
Follow-up Comment #6, bug #62227 (project findutils): [comment #5 comment #5:] > Okay, I agree. > > The attached patch changes the behavior (with the first one doing > a trivial cleanup), and I'd like to improve the documentation further in a separate patch. > > Please check. > > (file #53051,

[bug #62227] Incorrect warning for -name /

2022-04-07 Thread Bernhard Voelker
Update of bug #62227 (project findutils): Status: In Progress => Code Review ___ Follow-up Comment #5: Okay, I agree. The attached patch changes the behavior (with the first one doing a trivial cl

[bug #62227] Incorrect warning for -name /

2022-03-29 Thread anonymous
Follow-up Comment #4, bug #62227 (project findutils): [comment #3 comment #3:] > So for my understanding: > if 'find / -prune -name /' boils down to 'echo /', then what is > the real use case behind? In that case it does not do anything useful, sure. To get something useful we would need to add m

[bug #62227] Incorrect warning for -name /

2022-03-28 Thread Bernhard Voelker
Follow-up Comment #3, bug #62227 (project findutils): I'm just a bit reluctant because '-name /' will really only find a match if "/" is given as starting point (which we don't know at the time of parsing the expression tree). In all other cases it is better for a user to keep the simple rule in m

[bug #62227] Incorrect warning for -name /

2022-03-28 Thread anonymous
Follow-up Comment #2, bug #62227 (project findutils): [comment #1 comment #1:] > I personally like to get such a warning, as one should try to use -name/-iname > with patterns for basenames only, and I think that the use case 'find / -prune -name /' > is quite exotic (and I would never have tried

[bug #62227] Incorrect warning for -name /

2022-03-28 Thread Bernhard Voelker
Update of bug #62227 (project findutils): Status:None => In Progress Assigned to:None => berny ___ Follow-up Comment #1: It's true: even a

[bug #62227] Incorrect warning for -name /

2022-03-27 Thread anonymous
URL: Summary: Incorrect warning for -name / Project: findutils Submitted by: None Submitted on: Mon 28 Mar 2022 06:37:13 AM UTC Category: find Severity: 3 - Normal