Changes committed to git://git.pcp.io/kenj/pcp master
Ken McDonell (3):
src/pmcd/GNUmakefile: fix sed(1) usage
assorted service.in -> service makefile changes
qa/527: filter out another variant of the perl line numbering buglet
qa/527 | 3 ++-
src/pmcd/GNUmakefile | 2 +-
src/pmie/GNUmakefile | 2 +-
src/pmlogger/GNUmakefile | 2 +-
src/pmmgr/GNUmakefile | 2 +-
src/pmproxy/GNUmakefile | 2 +-
src/pmwebapi/GNUmakefile | 2 +-
7 files changed, 8 insertions(+), 7 deletions(-)
Details ...
commit d7fd423bbfbc49e9f149ba8cb0d1952330492ed7
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Sun Sep 4 17:48:13 2016 +1000
qa/527: filter out another variant of the perl line numbering buglet
commit e1d3cbb9319d95f4926e84ab6a5a6ad6a7167a84
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Sun Sep 4 17:07:24 2016 +1000
assorted service.in -> service makefile changes
Same sed(1) usage problem as fixed in the previous commit ...
The sloppiness from the GNU implementation of getopt* is not universal
and putting command line options after command line arguments is not a
good idea ... specifically sed file -e edit is not always acceptable,
and to be properly portable one needs to avoid this command line mess
and stick with the classical usage, namely sed -e edit file
commit 0189bdb8547f04c590a8dd081d47285865df92af
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Sun Sep 4 16:54:52 2016 +1000
src/pmcd/GNUmakefile: fix sed(1) usage
The sloppiness from the GNU implementation of getopt* is not universal
and putting command line options after command line arguments is not a
good idea ... specifically sed file -e edit is not always acceptable,
and to be properly portable one needs to avoid this command line mess
and stick with the classical usage, namely sed -e edit file
|