From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: m.olbrich@pengutronix.de
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] Add procps-ng, an improved version of procps
Date: Wed, 1 Jul 2015 16:00:32 +0200 [thread overview]
Message-ID: <20150701140032.GA4772@pqgruber.com> (raw)
In-Reply-To: <20150701081340.GH30833@pengutronix.de>
Hi Michael,
On Wed, Jul 01, 2015 at 10:13:40AM +0200, Michael Olbrich wrote:
> I think, updating the procps packages and using procps-ng there is the way
> to go. I don't think the original procps is updated any more and procps-ng
> seems to be based on the same code.
>
> Michael
>
Do you want to keep the package name "procps" and just change the URL and
some configuration options or should I send a v2 which deletes the existing
procps package and adds the procps-ng package?
Clemens
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-07-01 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 11:52 Clemens Gruber
2015-07-01 8:13 ` Michael Olbrich
2015-07-01 14:00 ` Clemens Gruber [this message]
2015-07-02 6:47 ` Michael Olbrich
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=20150701140032.GA4772@pqgruber.com \
--to=clemens.gruber@pqgruber.com \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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