From 3f865a76c5891b1664136decb4f2eb6ee5391f57 Mon Sep 17 00:00:00 2001 From: Eric Biggers Date: Mon, 13 Sep 2021 12:40:14 -0700 Subject: README: remove note about stability A lot of people are already using fscrypt, so in practice we haven't been breaking backwards compatibility and aren't going to. Just remove the scary-sounding "Note about stability". --- README.md | 10 ---------- 1 file changed, 10 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 285bb25..f6aa9d0 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,6 @@ native encryption. See [Runtime Dependencies](#runtime-dependencies). - [Enabling the PAM module on Arch Linux](#enabling-the-pam-module-on-arch-linux) - [Enabling the PAM module on other Linux distros](#enabling-the-pam-module-on-other-linux-distros) - [Allowing `fscrypt` to check your login passphrase](#allowing-fscrypt-to-check-your-login-passphrase) -- [Note about stability](#note-about-stability) - [Example Usage](#example-usage) - [Setting up fscrypt on a directory](#setting-up-fscrypt-on-a-directory) - [Locking and unlocking a directory](#locking-and-unlocking-a-directory) @@ -439,15 +438,6 @@ file `/etc/pam.d/fscrypt` containing: auth required pam_unix.so ``` -## Note about stability - -`fscrypt` follows [semantic versioning](http://semver.org). As such, all -versions below `1.0.0` should be considered development versions. This means no -guarantees are make about the stability of APIs or formats of config files. As -the on-disk metadata structures use [Protocol -Buffers](https://github.com/google/protobuf), we don't expect to break backwards -compatibility for metadata, but we give no guarantees. - ## Example Usage All these examples assume there is an ext4 filesystem which supports -- cgit v1.2.3