From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: btrfs versions compatibility and updates
Date: Mon, 13 Jan 2014 17:47:31 +0000 [thread overview]
Message-ID: <lb18r7$q52$1@ger.gmane.org> (raw)
There's the very good idea of releasing the btrfs userspace tools with a
version number that matches the kernel version... Good to see a good
jump for what is considered 'stable'.
What is the policy for maintaining compatibility with whatever range of
kernel versions?
And what is the state of play now for the "Chris Mason" or whatever
latest 'stable' branch of btrfs on git?
In other words: Should we always update the btrfs userspace tools to the
latest even though we may be running one or two kernels behind that?...
Thanks,
Martin
next reply other threads:[~2014-01-13 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 17:47 Martin [this message]
2014-01-13 19:30 ` btrfs versions compatibility and updates Calvin Walton
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='lb18r7$q52$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--cc=linux-btrfs@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