From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] pseudo-wrapper: fix console issue
Date: Wed, 23 Nov 2016 21:57:45 +0100 [thread overview]
Message-ID: <20161123215745.7c307e23@free-electrons.com> (raw)
In-Reply-To: <20161123182843.GA3609@free.fr>
Hello,
On Wed, 23 Nov 2016 19:28:43 +0100, Yann E. MORIN wrote:
> - long term, we want to definitely switch to using pseudo:
> - it is actively maintained,,
> - it has more features than fakeroot,
> - some of those features are very interesting for us.
Could you explain which additional features of pseudo are interesting
for us?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-23 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 17:36 [Buildroot] [PATCH v3] pseudo-wrapper: fix console issue Gaël PORTAY
2016-11-23 18:28 ` Yann E. MORIN
2016-11-23 20:57 ` Thomas Petazzoni [this message]
2016-11-23 21:34 ` Yann E. MORIN
2016-11-23 21:36 ` Thomas Petazzoni
2016-11-23 21:47 ` Arnout Vandecappelle
2016-11-23 23:59 ` Gaël PORTAY
2016-11-24 19:24 ` Arnout Vandecappelle
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=20161123215745.7c307e23@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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