[bug #30180] error message from incorrect -size option is off

Update of bug #30180 (project findutils): Status: Code Review => Fixed ___ Reply to this item at: ___

[bug #30777] using "-exec {} +" syntax silently gobbles excess strings

Update of bug #30777 (project findutils): Status: Code Review => Fixed ___ Reply to this item at: ___

[bug #30777] using "-exec {} +" syntax silently gobbles excess strings

Follow-up Comment #3, bug #30777 (project findutils): I've attached an updated patch (which I'm gong to push) which quotes the arguments. (file #21229) ___ Additional Item Attachment: File name: 0001-Fix-Savannah-bug-30777.patch Size:5 KB

[PATCH] Fix Savannah bug #30180, wrong error message for -size b300

* find/parser.c (parse_size): Don't print a suffix in the error message if no suffix was specified. * NEWS: Mention this change. --- ChangeLog |5 + NEWS |2 ++ find/parser.c | 11 --- 3 files changed, 15 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/Ch

[bug #30180] error message from incorrect -size option is off

Follow-up Comment #2, bug #30180 (project findutils): seems to work for me, thanks ___ Reply to this item at: ___ Message sent via/by Savannah http:/

[bug #30777] using "-exec {} +" syntax silently gobbles excess strings

Follow-up Comment #2, bug #30777 (project findutils): that seems to work ... should the error message be quoted at all though ? all the symbols seem to meld into the surrounding text. In '-exec ... {} +' the '{}' must appear by itself, but you specified '/usr/{}' __

[bug #28237] strange behavior (maybe a bug, maybe not...) [needs better explanation of the problem]

Update of bug #28237 (project findutils): Status: Need Info => Invalid Assigned to:None => jay ___ Follow-up Comment #5: The first senten

[bug #30327] regex ranges [A-Z] and [a-z] ignore case.

Update of bug #30327 (project findutils): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #30777] using "-exec {} +" syntax silently gobbles excess strings

Update of bug #30777 (project findutils): Status: In Progress => Code Review ___ Reply to this item at: ___

[bug #30180] error message from incorrect -size option is off

Update of bug #30180 (project findutils): Status:None => Code Review Assigned to:None => jay ___ Follow-up Comment #1: I believe this p

[PATCH] Fix Savannah bug #30180, wrong error message for -size b300

* find/parser.c (parse_size): Don't print a suffix in the error message if no suffix was specified. * NEWS: Mention this change. --- ChangeLog |5 + NEWS |2 ++ find/parser.c | 11 --- 3 files changed, 15 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/Ch

[bug #30504] bug/rfe....the "-P" option seems to be unusable by itself

Follow-up Comment #3, bug #30504 (project findutils): 'if the input is sufficiently large'? In my case it would have to exceed 2MB of characters. In a practical sense that means it would never use more than one. Thus my assertion that the algorithm is flawed. If a user _uses_ -P by itself,

[bug #30608] Automagic dependency on selinux

Update of bug #30608 (project findutils): Status:None => Need Info ___ Follow-up Comment #1: Sorry about my delay in response. Let me check I understood you: - you want to be able to

[bug #30504] bug/rfe....the "-P" option seems to be unusable by itself

Follow-up Comment #2, bug #30504 (project findutils): Clearly -P would result in parallel processing if the input is sufficiently large. It's not going to be possible for xargs to choose an optimal strategy; at any point it would need to be able to choose between reading another argument (which

[bug #29512] [feature request] xargs parallel processing env-val improvement

Follow-up Comment #14, bug #29512 (project findutils): I've updated the patch to target the current head revision. (file #21224) ___ Additional Item Attachment: File name: 0001-Implement-xargs-process-slot-var.patch Size:10 KB

[bug #29698] Correct and clarify documentation of xargs -d option

Follow-up Comment #2, bug #29698 (project findutils): (if no response within a couple of weeks, I'll close this bug) ___ Reply to this item at: ___ Mes

[bug #29828] Test suite deadlock on FreeBSD

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

[bug #30777] using "-exec {} +" syntax silently gobbles excess strings

Follow-up Comment #1, bug #30777 (project findutils): I believe the attached patch (against c530d90990ca81dfca254bbca18ab9e7273b4585) fixes the bug. (file #21223) ___ Additional Item Attachment: File name: 0001-Fix-Savannah-bug-30777.patc

[PATCH] Fix Savannah bug #30777.

* find/parser.c (insert_exec_ok): Fail if {} appears in an argument between -exec ... \+ but it's not the whole argument (that is, reject "FOO{}"). Previously the FOO prefix was accepted but ignored, which is probably POSIX-incompliant and certainly surprising. * find/testsuite/find.posix/sv-bug-3

[bug #30777] using "-exec {} +" syntax silently gobbles excess strings

Update of bug #30777 (project findutils): Severity: 3 - Normal => 4 - Important Status:None => In Progress Assigned to:None => jay __