From: Mike Frysinger <vapier@gentoo.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: v2.22 wish list
Date: Mon, 12 Mar 2012 13:50:43 -0400 [thread overview]
Message-ID: <201203121350.44028.vapier@gentoo.org> (raw)
In-Reply-To: <20120229154420.GD8471@x2.net.home>
[-- Attachment #1: Type: Text/Plain, Size: 222 bytes --]
On Wednesday 29 February 2012 10:44:20 Karel Zak wrote:
> This is my v2.22 wish list. The list contains large/invasive tasks only.
> Comments, volunteers, .... ? ;-)
how about merging killall5/pidof from sysvinit ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-12 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 15:44 v2.22 wish list Karel Zak
2012-02-29 16:02 ` Keshav P R
2012-02-29 16:25 ` Karel Zak
[not found] ` <CAG27Bk1kMB9Mw46T3Lb0DBttqDOrHU0JBTkSERd7rfL8ikvH8A@mail.gmail.com>
2012-03-01 21:51 ` Sami Kerola
2012-04-11 11:42 ` Karel Zak
2012-03-02 15:10 ` Karel Zak
2012-03-03 14:45 ` Petr Uzel
2012-03-12 17:50 ` Mike Frysinger [this message]
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=201203121350.44028.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=kzak@redhat.com \
--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