From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: kerolasa@iki.fi
Subject: [PATCH 0/7] kill: modernization after undeprecation
Date: Thu, 7 Mar 2013 23:27:17 +0000 [thread overview]
Message-ID: <1362698844-21292-1-git-send-email-kerolasa@iki.fi> (raw)
Hi Karel, et.al.,
Here are few patches to kill which was undeprecated late last year, see
commit 32fca0e9c49599667d19f157fade6fa46908271a. I had a look of the
command and decided it should get the same usage(), coding style, etc,
fixes that are done to other commands earlier.
The only notable change in this series is second last patch which will
make kill to use pid_t. I am sure that is better than having int
representing pids, altough int might often work. The patch also makes
some pid_t's to be casted long which may be a bit overkill. Perhaps it
is better to grant enough head room to pid space than cry when type wrap
results to kill of arbitrary process(es).
The following changes since commit 02658d9bb56976b462724b306e9e1f4385ef4b93:
tests: make utmpdump TZ independent (2013-03-04 13:10:09 +0100)
are available in the git repository at:
git://github.com/kerolasa/lelux-utiliteetit.git 2013wk09
for you to fetch changes up to 4f6dba8146a461dee9e62b5cf5ff62425ad01681:
docs: add long options and tidy up kill.1 (2013-03-07 23:08:53 +0000)
----------------------------------------------------------------
Sami Kerola (7):
kill: add long options
kill: align with howto-usage-function.txt
kill: use libc error printing facilities and exit values
kill, procs: fix coding style
kill, procs: move function declarations to kill.h
kill, procs: use pid_t for pids
docs: add long options and tidy up kill.1
misc-utils/kill.1 | 88 ++++++-----
misc-utils/kill.c | 442 ++++++++++++++++++++++++++---------------------------
misc-utils/kill.h | 8 +-
misc-utils/procs.c | 170 +++++++++++----------
4 files changed, 360 insertions(+), 348 deletions(-)
next reply other threads:[~2013-03-07 23:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 23:27 Sami Kerola [this message]
2013-03-07 23:27 ` [PATCH 1/7] kill: add long options Sami Kerola
2013-03-07 23:27 ` [PATCH 2/7] kill: align with howto-usage-function.txt Sami Kerola
2013-03-07 23:27 ` [PATCH 3/7] kill: use libc error printing facilities and exit values Sami Kerola
2013-03-07 23:27 ` [PATCH 4/7] kill, procs: fix coding style Sami Kerola
2013-03-07 23:27 ` [PATCH 5/7] kill, procs: move function declarations to kill.h Sami Kerola
2013-03-07 23:27 ` [PATCH 6/7] kill, procs: use pid_t for pids Sami Kerola
2013-03-07 23:27 ` [PATCH 7/7] docs: add long options and tidy up kill.1 Sami Kerola
2013-03-12 14:29 ` [PATCH 0/7] kill: modernization after undeprecation Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1362698844-21292-1-git-send-email-kerolasa@iki.fi \
--to=kerolasa@iki.fi \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox