From: Emmanuel Florac <eflorac@intellique.com>
To: Jan Tulak <jtulak@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [proposal] making filesystem tools more machine friendly
Date: Fri, 30 Jun 2017 15:58:08 +0200 [thread overview]
Message-ID: <20170630155808.7cbab344@harpe.intellique.com> (raw)
In-Reply-To: <CACj3i70p=ybXZWRncseqwnbs7HAYu-SL02+cj--7T5YnqcwVKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Le Fri, 30 Jun 2017 10:17:17 +0200
Jan Tulak <jtulak@redhat.com> écrivait:
> A structured output is something we should aim for. It helps a lot
> with the issues and it is the cheapest option. If it goes well, it can
> be later on followed by creating a library, although, at this moment,
> that seems a premature thing strive for. Creating a daemon is not a
> thing any single filesystem should do on its own.
>
> And thank you for reading all this, I look forward to your
> comments. :-)
The whole concept seems a noble endeavour, I'm a bit wary of the
possibility to convince all the teams in charge to adhere to it
however... But that looks like a good idea for sure :)
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-06-30 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 8:17 [proposal] making filesystem tools more machine friendly Jan Tulak
2017-06-30 13:58 ` Emmanuel Florac [this message]
2017-07-05 18:11 ` Christoph Hellwig
2017-07-12 17:10 ` Richard W.M. Jones
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=20170630155808.7cbab344@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=jtulak@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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).