From: David Disseldorp <ddiss@suse.de>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/1] btrfs-progs: btrfstune: print seeding status
Date: Fri, 4 Jan 2019 14:34:15 +0100 [thread overview]
Message-ID: <20190104143415.1a4d4296@suse.de> (raw)
In-Reply-To: <85b4bef0-20ae-9cac-5ddb-955fe2331a0d@suse.com>
On Fri, 4 Jan 2019 15:18:13 +0200, Nikolay Borisov wrote:
> IMO seed has really been
> hacked on "just because" and is lacking coherent design, I'd prefer it
> didn't proliferate and rely on what we have currently.
That's unfortunate to hear. Seed devices are IMO a very cool feature for
transactional OS updates and live installers.
Cheers, David
next prev parent reply other threads:[~2019-01-04 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 23:22 [PATCH 0/1] btrfs-progs: btrfstune: print seeding status David Disseldorp
2019-01-03 23:22 ` [PATCH 1/1] " David Disseldorp
2019-01-04 7:05 ` Nikolay Borisov
2019-01-04 10:26 ` David Disseldorp
2019-01-04 12:09 ` Anand Jain
2019-01-04 13:18 ` Nikolay Borisov
2019-01-04 13:34 ` David Disseldorp [this message]
2019-01-05 5:45 ` Anand Jain
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=20190104143415.1a4d4296@suse.de \
--to=ddiss@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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