From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 0/2] ipcs: more robust and compatible /proc parsing
Date: Fri, 18 Mar 2016 14:48:22 +0100 [thread overview]
Message-ID: <20160318134822.hx2f5byqrocdoysn@ws.net.home> (raw)
In-Reply-To: <1458301758-21853-1-git-send-email-sweet_f_a@gmx.de>
On Fri, Mar 18, 2016 at 12:49:16PM +0100, Ruediger Meier wrote:
> From: Ruediger Meier <ruediger.meier@ga-group.nl>
>
> If this looks ok for shm then we could also add similar patches for
> sem and msg.
Seems good, I'll wait for complete set of the patches, ok?
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2016-03-18 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 11:49 [PATCH 0/2] ipcs: more robust and compatible /proc parsing Ruediger Meier
2016-03-18 11:49 ` [PATCH 1/2] ipcs: make sure to parse whole lines for shm_data Ruediger Meier
2016-03-18 11:49 ` [PATCH 2/2] ipcs: --shmems, upward/backward compatibility Ruediger Meier
2016-03-18 13:48 ` Karel Zak [this message]
2016-03-18 14:03 ` [PATCH 0/2] ipcs: more robust and compatible /proc parsing Ruediger Meier
2016-03-18 14:38 ` 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=20160318134822.hx2f5byqrocdoysn@ws.net.home \
--to=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--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