From: Andrzej Jakowski <andrzej.jakowski@linux.intel.com>
To: Karel Zak <kzak@redhat.com>,
"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>
Subject: Re: Re: [RFC] utility for SED management
Date: Thu, 6 Feb 2020 16:08:53 -0700 [thread overview]
Message-ID: <4f66147e-8938-2fa2-b9ce-b92915798c70@linux.intel.com> (raw)
In-Reply-To: <20190614074828.iqgomebc6gilprkn () ws ! net ! home>
On 6/14/19 12:48 AM, Karel Zak wrote:
> On Thu, Jun 13, 2019 at 01:51:12PM +0000, Jakowski, Andrzej wrote:
>> On Wed, Jun 12, 2019 at 01:40:08PM +0000, Karel Zak wrote:
>>> From my point of view (and maybe I'm wrong ;-)) it seems complex enough to keep it as an independent stand-alone project ("sed-utils").
>>> Not sure if it makes sense to push it to generic util-linux package.
>> It sounds to me that your major concern for inclusion sedcli into util-linux is
>> its complexity. What would be the best method to understand if sedcli fits into
>> util-linux?
> Do you have the current code/repo with sedcli accessible anywhere? It
> would be nice to see it.
>
> Karel
Trying to resurect that thread.
Code has been published on github:
https://github.com/sedcli/sedcli
Andrzej
parent reply other threads:[~2020-02-06 23:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190614074828.iqgomebc6gilprkn () ws ! net ! home>]
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=4f66147e-8938-2fa2-b9ce-b92915798c70@linux.intel.com \
--to=andrzej.jakowski@linux.intel.com \
--cc=kzak@redhat.com \
--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).