From: <Fabian.Kirsch@dlr.de>
To: <kzak@redhat.com>, <util-linux@vger.kernel.org>
Cc: <asbjorn@asbjorn.st>, <rick@openfortress.nl>
Subject: Re: script(1) plans
Date: Tue, 19 Mar 2019 07:30:24 +0000 [thread overview]
Message-ID: <1552980724.5643.12.camel@dlr.de> (raw)
In-Reply-To: <20190318125322.4obb27vwtxfuwuie@ws.net.home>
> I'd like to improve script(1) to be more flexible and support more
Hi,
IMHO strace(1) needs an additional output format which is designed for
further processing instead of eye-balls.
And then script(1) could become one of the filters which cook raw
strace-logs into the format which fits its purpose.
Otherwise script(1) starts walking through the design space towards
strace(1), without factoring out the common part.
Greetings
Fabian
next prev parent reply other threads:[~2019-03-19 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 12:53 script(1) plans Karel Zak
2019-03-18 21:10 ` Martin Steigerwald
2019-03-19 7:30 ` Fabian.Kirsch [this message]
2019-03-19 7:53 ` Rick van Rein
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=1552980724.5643.12.camel@dlr.de \
--to=fabian.kirsch@dlr.de \
--cc=asbjorn@asbjorn.st \
--cc=kzak@redhat.com \
--cc=rick@openfortress.nl \
--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;
as well as URLs for NNTP newsgroup(s).