From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/7] package/procps: bump version and rename to procps-ng
Date: Mon, 02 Jun 2014 22:34:37 +0200 [thread overview]
Message-ID: <87lhtft5ia.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <c827e84d7c56c699982501adbc8fd01e8602ce10.1401740805.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Mon, 2 Jun 2014 22:27:22 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> procps is getting replaced by procps-ng, and there are
> new versions available!
> procps-ng is now an autotools package, so get rid of our
> custom build/install rules.
> Remove most patches, except for one that still half-applies,
> so update and rename it.
> procps is dead, long live procps-ng!
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-06-02 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 20:27 [Buildroot] [PATCH 0/7 v3] A bunch of bumps (branch yem/bumps) Yann E. MORIN
2014-06-02 20:27 ` [Buildroot] [PATCH 1/7] package/procps: bump version and rename to procps-ng Yann E. MORIN
2014-06-02 20:34 ` Peter Korsgaard [this message]
2014-06-02 20:27 ` [Buildroot] [PATCH 2/7] package/libinput: new package Yann E. MORIN
2014-06-02 21:15 ` Peter Korsgaard
2014-06-02 20:27 ` [Buildroot] [PATCH 3/7] package/weston: add support for libinput Yann E. MORIN
2014-06-02 21:16 ` Peter Korsgaard
2014-06-02 20:27 ` [Buildroot] [PATCH 4/7] package/freerdp: not forcibly depend on X.Org Yann E. MORIN
2014-06-02 20:27 ` [Buildroot] [PATCH 5/7] pacakge/freerdp: disable building the manpages Yann E. MORIN
2014-06-02 20:27 ` [Buildroot] [PATCH 6/7] package/freerdp: add options to enable/disable server and/or client Yann E. MORIN
2014-06-02 20:27 ` [Buildroot] [PATCH 7/7] [WIP] package/weston: add support for the RDP compositor Yann E. MORIN
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=87lhtft5ia.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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