Re: wc function proposal for an additional switch -? (choose letter ?

2015-05-19 Thread Mike Frysinger
On 03 May 2015 23:30, Leslie S Satenstein wrote: > While there is nothing wrong with wc as is, a suggestion after some use. > > With wc -l  it emits the line count  and the program name(s) as   "nnn  > program-name". > With the additional switch option, it would be convenient to drop the program

[PATCH] tests: fix non POSIX constructs causing failures with dash

2015-05-19 Thread Pádraig Brady
* tests/cp/no-ctx.sh: Scope of `var=val func` is inconsistent across shells, so avoid that construct with functions. * tests/df/no-mtab-status.sh: Likewise. * tests/tail-2/inotify-race.sh: `read` needs an argument. * tests/tail-2/inotify-race2.sh: Likewise. --- tests/cp/no-ctx.sh| 3 +

Re: [PATCH] tests: fix non POSIX constructs causing failures with dash

2015-05-19 Thread Mike Frysinger
On 19 May 2015 12:42, Pádraig Brady wrote: > * tests/cp/no-ctx.sh: Scope of `var=val func` is inconsistent > across shells, so avoid that construct with functions. i think POSIX requires the behavior dash exhibits, and bash will do the same when it's in POSIX compliant mode. > -LD_PRELOAD=./k.so

Re: [PATCH] tests: fix non POSIX constructs causing failures with dash

2015-05-19 Thread Pádraig Brady
On 19/05/15 13:45, Mike Frysinger wrote: > On 19 May 2015 12:42, Pádraig Brady wrote: >> * tests/cp/no-ctx.sh: Scope of `var=val func` is inconsistent >> across shells, so avoid that construct with functions. > > i think POSIX requires the behavior dash exhibits, and bash will do the same > when

Re: [PATCH] tests: fix non POSIX constructs causing failures with dash

2015-05-19 Thread Pádraig Brady
On 19/05/15 14:04, Pádraig Brady wrote: > On 19/05/15 13:45, Mike Frysinger wrote: >> On 19 May 2015 12:42, Pádraig Brady wrote: >>> * tests/cp/no-ctx.sh: Scope of `var=val func` is inconsistent >>> across shells, so avoid that construct with functions. >> >> i think POSIX requires the behavior das

test coverage notes

2015-05-19 Thread Pádraig Brady
http://www.opencoverage.net/ is now tracking coreutils and it's at 46% overage with their config and condition/decision coverage checking mechanism Also note the gcov results at: http://hydra.nixos.org/job/gnu/coreutils-master/coverage which currently result in: Summary coverage rate: lines.

sparse file processing improvements for dd

2015-05-19 Thread Pádraig Brady
On 08/10/14 15:55, Pádraig Brady wrote: > Subject: [PATCH 2/4] cp: avoid speculative preallocation with --sparse=always > > With --sparse=always use fallocate(...PUNCH_HOLE...) to > avoid any permanent allocation due to speculative > preallocation employed by file systems such as XFS. For the rec