From: Colin Walters <walters@verbum.org>
To: Lennart Poettering <mzxreary@0pointer.de>
Cc: Oleg Nesterov <oleg@redhat.com>,
Denys Vlasenko <vda.linux@googlemail.com>,
systemd-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [systemd-devel] [PATCH 2/2] coredump: Handle programs with spaces in COMM
Date: Sat, 04 May 2013 20:04:03 -0400 [thread overview]
Message-ID: <1367712243.6959.213.camel@localhost> (raw)
In-Reply-To: <20130503150824.GB24114@tango.0pointer.de>
On Fri, 2013-05-03 at 17:08 +0200, Lennart Poettering wrote:
> It sounds really wrong to first merge this into one string and then
> split it up again. It sounds much more sensible to instead just pass the
> string array around all the time. What's the reason to make this one
> string first?
I'm wondering if there are compatibility concerns; abrt wouldn't care
from what I can tell if we just changed the kernel. systemd-coredump is
just plain broken right now. I'll look for the source to the Ubuntu
one...
next prev parent reply other threads:[~2013-05-05 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1367341939.6959.1.camel@localhost>
[not found] ` <20130430174731.GC3394@in.waw.pl>
[not found] ` <1367349331.6959.80.camel@localhost>
2013-05-01 16:42 ` [systemd-devel] [PATCH 2/2] coredump: Handle programs with spaces in COMM Oleg Nesterov
2013-05-03 15:08 ` Lennart Poettering
2013-05-05 0:04 ` Colin Walters [this message]
2013-05-09 18:10 ` Oleg Nesterov
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=1367712243.6959.213.camel@localhost \
--to=walters@verbum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mzxreary@0pointer.de \
--cc=oleg@redhat.com \
--cc=systemd-devel@lists.freedesktop.org \
--cc=vda.linux@googlemail.com \
/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